In general, the Page sections do not collapse or expand based on their content. Also the report header and group header sections span the width of the column.
It would be nice if, for example, have another section that either could expand/collapse based on the content and do not be affected by the report's page settings.
Add the new Crystal theme to the theme ResourceDictionaries available for the WPF and Silverlight ReportViewers.
I would like the end user to be able to resize the DocumentMap and if possible the Parameters Area. Many times when the names are long they are cut off. Many of my user will have clients will have similar names like law firms with a particular attorney name appended. Example: LAW FIRM OF DOUCHE AND BAG - JAMES SMITH ESQ LAW FIRM OF DOUCHE AND BAG - KIM JONES With the current implementation it would be cut off before you could see the end of the name. LAW FIRM OF DOUCHE AN LAW FIRM OF DOUCHE AN This requires them to use the scroll bar back and forth instead of resizing the area like the old webforms viewer. Please see picture for references. Also if there was an option for the names to have tooltips so they could just hover that would be helpful. The parameter map at least will wrap the names that are long it’s the DocumentMap that is the bigger problem. Thanks John
When in Print Preview, allow the user to view more than one page at a time. Maybe using the zoom out or mouse wheel to show more and zoom in to show less. Thanks!
As for now, from the supported rendering extensions, only the PDF renders a document map as Bookmarks pane. All other rendering extensions ignore document maps.
It would be nice to have Document Map in Word documents too.
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
- OrderID
- ShippingAddressID (FK => AddressID)
- BillingAddressID (FK => AddressID)
- ...
Table B: Addresses
- AddressID
- AddressLine1
- ...
If both tables are selected in the query builder, you will get the following columns:
- OrderID
- ShippingAddressID
- BillingAddressID
- AddressID
- AddressLine1
- ...
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:
- OrderID
- ShippingAddressID
- BillingAddressID
- ShippingAddressID_AddressID
- ShippingAddressID_AddressLine1
- BillingAddressID_AddressID
- BillingAddressID_AddressLine1
- ...
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.
Hello,
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?
Best regards
Marc
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.
Reporting webapi to support asp.net core
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()));
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).
I understand that for most users, relative URLs don't make a lot of sense in reports. However, we want export our report to PDF and link to other PDF files *in the same directory*. As everything will be distributed as a ZIP file, we cannot know the absolute file path. It should be easy to support this as this is supported by PDF out of the box. Apparently, somewhere in the Reporting code, you remove URLs if they are not absolute. Just remove that check, let us put whatever we like in the hyperlinks. Thanks.
Provide a component which wraps the HTML5 Report Viewer for use in a Vue.js application. The HTML5 Report Viewer is built using Kendo UI for JQuery components. So, one can consider the approach covered here: https://laravel-news.com/vue-wrapper-component
I'm trying to learn more about your reporting tool, but your demo only shows me a blank page. https://demos.telerik.com/reporting/dashboard?&skinName=default
It would be very useful to have the option of changing Sort and Toggle Visibility icons for example to a vector image. Default png is not looking good when the report is scaled or in specific styles. Attached an example.
Currently there is no way to implement a table with html. It is pretty clear from the 1 ticket already open that this is not going to be done as it has been open for ~4 years at this point. Due to implementation challenge of the task, I suggest allowing for a HtmlTextBox to take the place of a TextBox in the table object. This will allow for better conditional formatting in a table, without having to implement the entire table function of Html.