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.
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 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>
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.
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.
With a complex DataModel structure, when interface is used, interface inheriting from other interface become a must. Unfortunately, this don't work with ObjectDataSource, as it only look at its level for properties, not in parent. Properties collecting should be done like this: var properties = typeof(IFoo).GetProperties().Union(typeof(IFoo) .GetInterfaces().SelectMany(t => t.GetProperties()));
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!
Please add support for signing PDFs with a certificate stored on a hardware token, for example on a Qualifies Signature Creation Devices (QSCD) as defined by the EU law known as EIDAS, using a native platform way (on Windows this might mean through the Certificate.msc store).
Please add support for Data Matrix barcodes. As of Q3 2014 this is the only format we will still need to rely on another library to create an image that is placed in a picture box. We would much rather be able to use the Barcode control for all our barcode requirements.
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.