Currently the query builder (in the Report Designer) cannot automatically build queries if there are multiple separate relationships connecting two tables.
Here's an example:
Table A: Orders
Table B: Addresses
If both tables are selected in the query builder, you will get the following columns:
In other words, only one copy of the address data is pulled in, despite the two separate FK relationships. I would expect something like the following:
We ran into this issue because we are using Telerik Reports to provide reporting for a data warehouse, and we have multiple relationships in our "table A" pointing to a date dimension (our "table B"). The current workaround for this is to write your own SQL queries instead of relying on the query builder, but we would like for our business users to be able to create reports on their own, and they don't know SQL.
Allow the WPF viewer theme to be set using resources for the current window instead of setting resources on application level. Now the theme can be set using <Window, but this approach will not work for the Search window, which is a separate window and therefore fails to resolve its styles.
Add progress bar that indicates when the report would be fully rendered.
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.
Several community members asked about a Report Viewer suitable for Vue.js applications. We will appreciate your feedback in this feature request. You can leave a comment with details about functionality requirements for a Vue.js Report Viewer e.g. initial setup, updates of the displayed report and ways of passing report parameters' values. Thank you.
We display data inside an HtmlTextBox that was entered using the RadEditor. It would be great if the Reporting HtmlTextBox could be brought much closer or even in line with tag support as the editor. We are frequently running into issues with uncommon tags (that we strip out for the HtmlTextBox) and also with spacing being different. We work around the issues we have, but continuing increased tag support or auto stripping of unsupported tags would be very appreciated.
We create many legal forms, which use nested ordered lists. In htmlTextBox for reporting, we'd like to apply styles like upper-alpha, lower-alpha, etc to the ol tag. Currently, the only numbering for an ol is 1, 2, 3. CSS ability to set the style at depth (like ol ol) would be best. <ol> <li>1. text</li> <li>2. text <ol> <li>a. text <ol> <li>i. text</li> <li>ii. text</li> </ol> </li> <li>b. text</li> </ol> </li> </ol>
While processing, if Barcode item throws an exception (for example "Barcode is too large to fit!"), the report's Error event is not fired.
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.
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
A ReportViewer control compatible with the Kendo Angular UI Framework (not the Kendo Jquery..).
When importing the css files into a project using the new Kendo angular UI framework (ngx) a lot of the components
of kendo are getting broken.
Or is there some workaround?
When a report with a document map is reloaded due to parameter change, the currently selected position in document map tree is lost and the current page number is reset to 1. Preserving the page number does not make sense, because changing a parameter may change the rendered pages count, hence there is no guarantee that the same page number will correspond to the previously examined page.
However, the viewer can persist the currently selected items hierarchy in the document map tree and try to select the same nodes after the report is reloaded. This would be particularly useful in Report Book scenarios where the book will navigate to the same report once the parameters are changed.
Steps to reproduce the problem:
1. Open the Report Book demo.
2. Navigate to Dashboard report by clicking the third item in the Document Map pane.
3. Change a report parameter, i.e. select 2002 in the Year parameter editor.
4. The viewer reloads the report book and navigates to its first page, clearing the highlighted items in Document Map pane.