It would be nice to have a report viewer component that does not rely on the full .net framework as described here. https://docs.telerik.com/reporting/html5-report-viewer-asp-net-core-2. I have a project that is not built against the full framework and would like to integrate reporting without converting all of my projects.
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.
Please add full support for asp.net Core. What you currently have is not nearly complete. We need to be able to use the report designer and add reports in a .net core project and we need to be able to use reports that have objectdatasources. Currently object datasource does not work with .net core dll's.
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
Support generating reports on .NET Core running on a non-Windows platform, esp. macOS or Linux-like OS.
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!
Ability to localize Standalone Report Designer created reports without the need of using custom functions.
Need to support installing and running reporting server restful API from within linux.
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()));
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.
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
The documentation is syntax prone to errors and does not follow well for new developers. The example code shown usually shows one step, please elaborate and show examples in depth for each topic. I have noticed in the forums that people have been complaining about errors in the documentation for more that two years and its still not fixed. I also see a lot of references to code that is shown in documentation that is obsolete or not yet implemented. The video series posted in the last few months (Q1 2015) are videos from 2009. Why?
Add Telerik Windows Form Report Viewer configuration option to use Image rendering based on a Bitmap instead of a Metafile. This will enable the hosting of Telerik Reporting REST Service in Azure AppServices for Windows Forms Report Viewer usage.
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, the Graph item ignores missing data points and always connects data points which have values. According to the "Displaying Missing Values and Incomplete Periods in Time Series" paper (https://www.perceptualedge.com/articles/visual_business_intelligence/missing_values_and_incomplete_periods_in_time_series.pdf) this approach of ignoring missing values is not recommended. The preferred approach (with gaps for missing values) is described in detail in the paper.