It would be good if the table headers can be frozen. This can be really useful in case of a big report which is displayed on a single page.
For our Customers a major drawback to creating form type reports (Invoices, Purchase Orders etc.) using Telerik Reporting is the inability to show vertical dividing lines between data columns in the 'Detail' section of the report that extend all the way down the page to the Page/Report footer. We were able to do this with Crystal Reports. But we plan to migrate all our Crystal reports to Telerik.
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.
When generating a report with multiple tables provide the ability to send these tables to different workbook tabs when exporting to Excel
It would be very helpful for us people that have been using Telerik Reporting in Silverlight (or WPF) applications to have access to a Report Viewer for Windows Store Apps (XAML). The future of Silverlight is unclear at least and there are many Line Of Business Applications currently running under Silverlight and I know of many developers that are looking to port their LOB apps to Windows Store Apps (or Universal Apps). The current HTML5 Report Viewer does not provide printing when it is implemented in browser window in Windows Store Apps so we cannot really offer this option to our customers.
I had a very challenging time getting Telerik Reports to work with my business objects. I'm not the only one -- see this thread: http://www.telerik.com/forums/how-to-use-object-data-source-in-report-designer This could be improved by: 1. Don't make users manually edit <Telerik.Reporting>. Create a UI in the designer where DLL's can be manually selected. 2. If there are errors loading the DLL's in <Telerik.Reporting>, tell the user, rather than failing silently, which is the current behavior. Importing reports from DLL's has the same silent-failure behavior: if there's something not quite right about the DLL's (wrong architecture setting, for example), you just see "no reports to import" rather than the actual error (bad file format, or whatever). I think a little work on the user experience around custom business objects would make new users who want to use the stand alone report designer in this way much happier. I was really surprised and frustrated that a modern product would fail like this with no exposed error messages.
Add the ability to specify rounded corners for the border of TextBoxes, Pictures, Tables and all other similar controls.
In the standalone designer, it would be helpful if you could drag and drop the column headers to reorder. At present you have to add a new column and delete the old one, remembering to copy all properties.
To have a better performance would be nice to cancel report rendering automatically or manually. If I am asking for a big report and after I change parameters and request new report, the previous request is still in progress and it is not going to be cancelled. Therefore I see high memory consumption on continuously refreshing a reports with a big data and after some time I see complete slow down of the Reporting Service and of course slow down of the server itself. The memory in this case is not released and Reporting Service crashes sometimes.
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.
We use Telerik's report books extensively - and find that to be a very powerful way to create dynamically generated reports. The feature request is: if a report's datasource doesn't fetch any rows don't add a blank page to the report book.
It would be good a maintain the scroll position on the parent page while navigating back from a drill-through report (using the back button of the report viewer) specially if the parent page contains a vertical scrollbar. This would enhance the user experience and eliminate the need to scroll back to the original position.
Why is it that the telerik report designer is locked down and cannot be used as a set of controls in a custom application as any other telerik control. We would like to use the report designer controls in an application we make to give it our look and feel and so we can give it the functionality we require. Why limit your customers by locking down your report designer. One of the great things about telerik is a great set of products and customer support. If we had a way to get at the Telerik.ReportDesigner.Core.dll we can figure our where the controls are and display them in our app. I don't understand the marketing behind the locked down report designer. How does it benefit your customers? You can still have a locked down designer for those customers that don't want to customize it. Providing access to Telerik.Reporting.Core.dll will give your customers the ability to customize the report designer to their needs. Telerik sells controls that customers use to make applications that they sell, so whats the difference with the designer?
It's currently not possible to define in the HTML5 Report Viewer "per Report" the available Export formats. It's also not possible to alter the List in the given JS Events because the List of PDF,XLS,etc is loaded on MouseOver in the menu. Would be great to have some kind of options, array list in the widget options to define what export formats are displayed. Kind regards, Otto.