Ability to localize Standalone Report Designer created reports without the need of using custom functions.
All Telerik Reporting assemblies to be distributed via Nuget packages, in order to ease deploying a solution that uses Telerik Reporting and to share the solution with other developers. Note: Without having Telerik Reporting installed on the machine, there will be no design-time support (Upgrade and other wizards, VS Report Designer, etc.). The purpose of the packages is only deployment.
Some reports contain a lot of detail (audit reports, sales reports). Users need to quickly find transaction numbers, etc. when balancing financials.
Can the Telerik Reporting libraries be available for install as a NuGet package that can be hosted on a local NuGet server? Hosting on the public NuGet server would be even better, but I would imagine that would be harder to get approved.
Hello, RadPdfProcessing supports PDF/A 1-3 since Q1/2015. It would be nice if the Report engine would also support PDF/A exports. PDF/A will bevome the future european standard for invoicing (ZUGFeRD) and is the current standard for long time archival of digital documents. Regards, Chris
Currently, if you wish to hide extra details on the second page of a report, the space taken up by the area is left blank which looks terrible and not conducive to professional report design. Related threads: http://www.telerik.com/forums/different-page-header-on-first-page http://www.telerik.com/forums/hiding-the-page-footer-leaves-a-blank-space-in-the-report Unfortunately using report books for this is not a valid option. Using the Report Book means quite a bit of extra work when all you need is for the second page to not have an glaring empty space. If I understand the process correctly, this means creating 2 reports which are nearly duplicates plus merging with Report Book for each 1 report that you are developing. This is unresonable to expect from enterprise shops that will develop hundreds of reports. I urge you to review your implementation in order to find a way to implement this feature in the future.
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.
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