Please provide the possibility to localize the HTML5 Report Viewer UI in a way that doesn't require modifying the template. It's already possible to localize the messages shown by the HTML5 Report Viewer as shown here: http://www.telerik.com/help/reporting/html5-report-viewer-localization.html Something similar for the actual UI would be great.
Allowing custom actions would greatly increase the power and flexibility of reports and the report viewer. While the current set of actions provide great functionality, they are still somewhat limited in scope. If actions were able to handle their own execution instead of having the individual report viewer implementations handle their execution, customers could enhance the functionality as they see fit.
Can you create a nuget package for the Telerik.ReportViewer.Wpf.Themes.dll.
Please note that Cc field is empty on server side.
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.
On attempt to display reports in Print Preview in Angular applications, an error is thrown if continuous scrolling is enabled.
Possible workaround: Disable continuous scrolling by setting the pageMode option to 'SINGLE_PAGE'.
While processing, if Barcode item throws an exception (for example "Barcode is too large to fit!"), the report's Error event is not fired.
In Standalone designer, when the Localizable of the Report is set to True and a new Language is selected, there is an "Object reference not set to an instance of an object" error.
Workaround: save the document after changing the culture/language, close the report, and then re-opening the saved report in the designer.
Telerik.Reporting.OpenXmlRendering.2.7.2.dll from the latest release (R1 2009) references the from version of DocumentFormat.OpenXml. See the screenshot:
Here the screenshot for the prev version (R3 2018 SP2):
Because of this our projects referencing DocumentFormat.OpenXml 2.8.1 (the latest version) are all broken. Xlsx rendering simply does not work anymore.
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!
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()));
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