The ObjectDataSource component in the Web Report Designer does not have complete design-time support. The major things that are missing:
Do you have an updated road-map or plan to support Web assembly (WASM), especially Blazor? You already published Blazor articles in your blogs.
It will be a good idea to add a new report viewer based on Blazor, protecting the parameters between the viewer and its API controller.
Also, will be a very good idea to start your online report designer (like alternative products), based on web assembly
We'd like to distribute the standalone report tool to our clients and provide data through a web service. We don't want to have to redistribute a dll everytime we make new data available. The standalone report tool should be able to query our webservice for what data is available and then allow the client user to create reports from it. i.e. obtain list of table names dynamically as well as their column names and data. A possible solution is to allow the tool to view and interact with classes in an external assembly that are dynamically generated with Reflection.Emit.
I can see that we can operate over a file definition using save, open, and save as. It would also be nice to be able to download the report definition as well.
Generated PDFs do not have bookmarks in R2 2021 unless there is a TOC section in the report.
By setting the device info setting "ProcessItemActions", the generated PDFs have bookmarks again.
var reportProcessor = new Telerik.Reporting.Processing.ReportProcessor(); var reportSource = new Telerik.Reporting.UriReportSource(); reportSource.Uri = "some Uri"; var deviceInfo = new System.Collections.Hashtable(); deviceInfo["ProcessItemActions"] = true; reportProcessor.RenderReport("PDF", reportSource, deviceInfo);
When groupings in a cross tab or merged row table span multiple pages the actual row label should be carried over to new page along with a label of some sort (if desired) to mark group is being continued from previous page.
A possible solution would be to expose a ParametersAreaLoaded and ParametersAreaUpdated events with the needed arguments.
This will make migration from Silverlight easier. There the user has a direct access to them through the ReportViewerModel.
running your https://demos.telerik.com/reporting in Chrome 77.0.3865.75, when trying to print the following error is returned:
Refused to execute script from 'https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=1ddd0495-ceb5-4cd4-b879-03f7c6be269b' because its MIME type ('image/gif') is not executable.
and nothing happens.
wasn't this fixed in your latest update?
is there a workable solution for this issue?
Implementing Drag&Drop for the Web Report Design is a major step toward feature parity with the Standalone Designer, and helps end-users leverage their established workflow when migrating to the Web Report Designer.
I'm not reporting an issue here, just making a suggestion about a minor change that I would consider as an improvement.
I'm loading at runtime a report template that was created using the standalone report designer. I'm dynamically replacing all the 'DataSources' of the report, and thus I have to go through all the items of the report to find them all.
The first step is to flatten all the items with a recursive call, starting from the 'Report'. I get a list of ReportItem, and I can cycle through this list and find those that inherits from 'DataItem'. From there, I just have to pick all the distinct DataSources from these DataItems.
And it almost works, except that I'm missing the DataSource from the Report itself, as the Report class does not inherit from DataItem but implements IDataItem.
If IDataItem was public, I could simply use it instead of 'DataItem', but as it is internal I have to handle a special case. And I don't like that.
Maybe I'm missing a good reason to keep this interface internal, but if not my suggestion is to make it public.