On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page.
For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again. The last two items should be numbered (4) and (5).
In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.
The attached file shows both these issues.
While configuring the WebServiceDataSource with the wizard if an error occurs on the Preview page, show the setup request details.
During runtime show the request details in the application trace.
Export options can be limited through the application configuration file, where the settings will be applied to all viewers and for all reports. For more info: Limit export options in ReportViewer to certain format only.
It would be nice to have specific export options per report without the need of building custom UI to handle the export.
When a report fulfills the following conditions :
1. Is Multicolumn;
2. Has DocumentMapText set;
3. Contains a List (data item) with DataSource set with Bindings to a field of the Report DataSource.
and is displayed in PrintPreview mode in the WPF Report Viewer, an exception like :"Could not register named object. Cannot register duplicate name '_20aa3785775c4790ba0cfa8021bd8433' in this scope.' Line number '1' and line position '2567'. Cannot register duplicate name '_20aa3785775c4790ba0cfa8021bd8433' in this scope." is thrown.
We need the ability to automatically adapt report layout after its page size chages using report elements docking, anchoring etc. functionality.
This will allow us to reuse report templates for different printer paper sizes without making specific report for each paper size.
We do not have knowledge of internal report layout composition so a layout changes cannot be done with custom code, but need to be specified in reports directly.
I suggest that when saving reports as trdx files (trdp files are no good as they are compressed), that you save the SQL on multiple lines as it appears in the designer to enabled version comparison, i.e. git history of the file's changes can show the changes to the SQL. Currently the SQL is on one line making it difficult to see the history.
Use only components from KendoUI for Angular. It would be understandable that such report viewer would provide less features, but it would remove dependency from jQuery and KendoUI for jQuery.
Actually multi value parameters is not supported on WebServices source. Multi value are passed as [string1,string2] instead of $paramName=string1¶mName=string2. Multi value has to be passed on query string on correct way!
Loading huge DB schemas is time-consuming. Add on-demand schema loader for the table columns schema in order to improve the user experience when using DB with a huge schema.
There is the newly introduced WebServiceDataSource which enables me to get JSON data from a web service. I'd like to be able to use JSON as a data source for a report without using a web service. For example, the JSON might be embedded inside the report definition, or it might be coming from an external text file (URI or URL), or even pass it programmatically to the report at run-time.
It would be really useful if EntityDataSouce was updated to support Entity Framework Core contexts. EF Core depends on Standard 2.0 so can run on .NET Core or the full framework.
In some cases, the data source might have dynamic columns meaning that the columns might change for different report runs. I need to be able to detect if a particular column is available using an expression so that I can handle its absence without showing an error to the end user.
It would be nice if resx files to localize the (wpf) report viewer can be placed in a specific resource path instead of the main folder of the VS project. For example a 'Resources' folder within the 'Properties' folder of the VS project.
First, we need the ability to have the controls in a Page Header Band to Grow/Shrink based on their contents. Second, the Page Header Band also needs the ability to Grow/Shrink based the first Condition and any other Conditional Formatting settings of controls with in that band. This is request becuase of the design of the Report Header Band and how it is designed for Multi Column Reports. The Report Header Band does all what I am asking for, however, in a Multi Column Report, it's only the size of the column width, which is a problem for some of our reports. We need it to be the entire page width. Some suggests to create PAGE BOOKS seems a bit complicated to do for such a simple request. I have been using different report writes in my 25+ years of programming, and Telerik Reports is the first one that I have used, that has these limitations..