We display data inside an HtmlTextBox that was entered using the RadEditor. It would be great if the Reporting HtmlTextBox could be brought much closer or even in line with tag support as the editor. We are frequently running into issues with uncommon tags (that we strip out for the HtmlTextBox) and also with spacing being different. We work around the issues we have, but continuing increased tag support or auto stripping of unsupported tags would be very appreciated.
If you do a Excel export, it renders the headers value, which we set with an expression (customer specific localised text), but as CSV the header names/IDs are used. It would be nice to have a 'Export Settings' category on the page properties, see attachment for example. Also shows another useful feature of disabling export option easily per report.
Our clients enter information using the radeditor and in many cases want to embedded tables and graphics into their text. Using your reporting tool there is no way to print this information. I know you have suggested using your table and image tools, but that doesn't work when you are dealing with freely formatted text so the existance and location of the tables and images cannot be predicted.
The problem: I have a table that has several million records. I have a report with parameters to query those records. Example on a sales report: Customer (All or specific customer) and Product (All or specific product) and date range. If by mistake the user selects all customers, all products, and a date range of 10 years, he may get millions of records for the report. After several seconds he realizes that he entered the wrong parameters and wants to cancel the report. There is no way to cancel. The solution was to run this in another thread and kill the process. That seems like a hack and doesn’t stop the web request so the web service keeps working even after the report has been killed.
Change request: Allow canceling in two ways:
The web data source should implement the “Cancellation Token” and cancel the web request when the report is canceled. Postman, browsers, and other tools use this technique so that the web service understands that the data is no longer needed and it can stop the request.
Some links explaining how to implement Cancellation Tokens:
After R1 2019 Telerik Web Report Viewers use Kendo splitter for resizing Parameters and Document map areas. At this point, there is no way to change the Parameters Areas position.
It would be extremely useful to have a Crosstab export the entire hierarchy as groups in Excel. SQL Reporting Services does this when exporting a report created there. I realize that this would mean generating the entire dataset prior to the export in order to expand all the data, but as I said, SSRS does this without a noticeable performance delay.
I am using the standalone report designer with an ObjectDataSource that returns ExpandoObject. I did create some new ExpandoObject objects and set property values as suggested in https://www.telerik.com/support/kb/reporting/details/how-to-use-objectdatasource-with-expandoobject. The problem I have that the dynamic properties of ExpandoObject are now showing in the data explorer.
If the controls and PDF generated from Designer or API from scratch will be 508 compliant? PDF needs to be tagged, so when a reader reads its images have text alternative for it to read.
I'm not a PDF expert, but if something can be done in a free library, a pay'd version of reporting tools should do it also right. In many cases, I do a report to PDF for my clients. Since PDF contains useful data, I't normal to assume, client will use copy-paste and copying data to Word, Browser, etc. Similar approach was used, when I created a project for the General prosecution of SR, but there the PDF was generated by PdfSharp and by writing text-outputs (with esired font, size, etc.). The result was correct. Unfortunatelly with Telerik it's not so. I've tryed to explain it in a ticket, but I only got excuses, explanation about lignatures and so. I got/left myself almost convinced, but my main point is the starting sentence in this description. The original issue: http://www.telerik.com/account/support-tickets/view-ticket.aspx?threadid=893196