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!
Loading huge DB schemas is time-consuming. Add on-demand schema loader for the table columns schema in order to improve the user experience when using DB with a huge schema.
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).
There is the newly introduced WebServiceDataSource which enables me to get JSON data from a web service. I'd like to be able to use JSON as a data source for a report without using a web service. For example, the JSON might be embedded inside the report definition, or it might be coming from an external text file (URI or URL), or even pass it programmatically to the report at run-time.
It would be really useful if EntityDataSouce was updated to support Entity Framework Core contexts. EF Core depends on Standard 2.0 so can run on .NET Core or the full framework.
In some cases, the data source might have dynamic columns meaning that the columns might change for different report runs. I need to be able to detect if a particular column is available using an expression so that I can handle its absence without showing an error to the end user.
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.
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.
First, we need the ability to have the controls in a Page Header Band to Grow/Shrink based on their contents. Second, the Page Header Band also needs the ability to Grow/Shrink based the first Condition and any other Conditional Formatting settings of controls with in that band. This is request becuase of the design of the Report Header Band and how it is designed for Multi Column Reports. The Report Header Band does all what I am asking for, however, in a Multi Column Report, it's only the size of the column width, which is a problem for some of our reports. We need it to be the entire page width. Some suggests to create PAGE BOOKS seems a bit complicated to do for such a simple request. I have been using different report writes in my 25+ years of programming, and Telerik Reports is the first one that I have used, that has these limitations..
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
One of the main features the clients require when exporting the reports to XLS or XLSX is to have the page width already set to 1 page. But for none of these exporting options, this is possible, unless you intercept somehow the export functionality prior to rendering the document to the client