I have a use case which requires me to record data whenever a report is printed. In pursuit of this, I am trying to replace the build in Print() tool and replace it with my own.

I have read this documentation which shows how to remove and reorder the buttons well enough, but it does not support adding a new tool all-together. Javascript event listeners will not work for me because ultimately what I want to do is accomplish a database write, which would be insecure through javascript.

 I have been able to establish a workaround by following this documentation and creating a button *outside* of the ReportViewer, however, I would still like to find a way to put the button inside of the ReportViewer toolbar if possible. 

I have updated to version 19.2.25.813 of Reporting, and when I try to build a project that has Reporting references, I get the following warnings:

Telerik and Kendo UI Licensing warning TKL102: Your current license has expired and is not valid for Telerik Document Processing Libraries version 2025.2.807.20.

There are no Telerik Document Processing dependencies in my project, but I still get the warning.

This bug has been reintroduced in 2025 Q3: https://feedback.telerik.com/reporting/1671864-2024-q4-pdf-rendering-made-text-extraction-impossible

I use the kendovalidator before rendering the report to check the correct parameter of initial and final date.

However, the validation fails because additional inputs (for the "Send Email" functionality) are included in the HTML output of the viewer even though I have disabled it.

I believe that if the "Send Email" option is disabled the mail data panel should not be created.

When adding an embedded image to a coded report in the Standalone Designer .NET, the original RESX file is not modified.

Only the original DESIGNER.CS file is modified. This leads to the new PictureBox being present but empty after deleting the dedicated folder named after the report (beside the designer EXE).

When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.

Additionally, images whose AccessibleDescription I have set may be read multiple times..

Graph markers, it would be nice to have a few more marker types for the chart, I would really like a up and down arrow, or a reversed triangle. also a left and right arrow/ triangle, and how about a star?

Hello,
I already developed in the past with your WPF controls and I'm mostly very happy. The controls are nice and the programming model (MVVM) is well done. I always recommend your controls the all my friends developer out there.
For a new project, I'm evaluation the Report Design + Viewer and I must say I'm very disappointed by the all product. 
First the general looking and feel seems coming from an old Visual Basic 6 age with outdated button toolbar + gui; non sizable dialogues like the one to choose fields (attached) With data source coming from entity model, the field and navigation property are often long and this is painful and useless to scroll horizontally to see the field name.
Coming back to data source, the report wizard is also confusing asking for an data source name rather than asking for an existing connectionstring and then create a new one for your need internally if needed. Also, the experience with an existing data model object is poor because the Data Member question is not obvious and when I select one the entity table, the wizard prompt with an alert see capture attached. If I don’t select any member, no alert but the field list is useless because I don’t see any field (see capture).
In conclusion, it seems to me the Report components are not done by the same team or at least are not develop in the same spirit and quality than the other controls.
I hope you will bring us a brand new controls asap.
Thanks for reading me 
Best regards
-Vince

Telerik.reportdesigner.exe crash with Null reference exception when add new object datasource with "Choose a data source member".

In the attached photo, I combined the first 2 pages of the PDF I get when I export the reports as a PDF (there were 198 pages in total). The second page is the continuation of the bar chart, as the bars expand. This is not readable or insightful to a user who wants to view the report, as he/she can not see any of the labeling of the X or Y axis on the second page. I would like to see labeling of both the X and Y axis on each page, so that the reports are easier to read. The same applies for graphs, columns, and table reports as well. 

It's confusing which rule does what by looking at the current UI...would be nice to give them aliases\friendly names which mean something when you go back 2 months later, know what I mean?

I've been using the Stand Alone Report Designer a fair bit lately but find myself having to switch between the Home, Insert and Data tabs quite a bit. It would be a great time saver if the Report Designer had a dockable toolbar (defaulted to the right) like in Visual Studio with short-cuts to adding things like Text boxes, pictures, etc.

Regards

Edu

Presently, when you use the Fields property, you can only access simple type properties : "= Fields.CompanyName", "= Fields.CompanyPhone". The complexe types are not accessibles via the Fields property. If you want to print a complexe type property, you need to use the expression "= ReportItem.DataObject.Company.Name", "= ReportItem.DataObject.Company.Phone".

In my opinion, this is not very intuitive. 2 differents ways to read a property depending of his type! It would be great to be able to access anything from the Fields property.

Without code behind, with a conditional formating changing the Visibility, to avoid empty space in the final report, the control must have its Height put to 0. But then it isn't visible anymore in the designer.
With a DesignHeight, it could be still visible in the designer.
The other solution would be to be able to change the Height in conditional formating.

When using report templates, the only connection with the original template is when the report is created. This is problematic due to the time it takes, as well as the potential for error and inconsistency.

It would be helpful if the report designer included an ability to update a report based on the template. If a minor change needs to be made to a group of reports, now that change has to be done individually in each report. Ideally there should be an option to update the report from the original template. While I understand that detailed content would be problematic to update, things such as styles, report and page headers/footers, etc., could be updated (or 'replaced' with the equivalent content from the template). 

Ideally there would be an option to update from template, and then the user could select which items to update; 
- styles
- page header/footer
-report header/footer

I like how with Kendo UI for MVC you have the option of placing the references dlls into lib/kendouimvc, so projects are not dependent on having the correct version installed (or having the telerik control panel installed on a build server), and when updates occur it will copy over everything and make sure you don't miss something. 

It would be nice to have an option in the upgrade wizard extension thingy to have a section for including telerik reporting and it will put the necessary dlls in your project the same way.

I can easily manually copy the files over, so this is just a pet peave thing, but it would be nice...

Possibility to select BarCode Encoding based on value on record dataItem.

I am using Telerik Reporting with MVC 5, and would like the ability to use the custom parameterEditor with MVC. If anything, I'd like to be able to create it with razor MVC, and then use jquery to add the parameterEditor.

It would be nice to have an image filter option when exporting reports to PDF. For example we need to export an image to PDF using the "Flate" algorithm so that the image is not compressed in any way.