I just rendered the attached report PDF with 19.2.25.813. The underlying text is garbaled, meaning search and copy don't work.

We use Telerik reports for many different things.  We generate reports, letters, mailings, excel documents and forms or applications.  Our applications can either be blank or pre-filled or completely filled with information from the user.  Now I realize that you can say that all of these are forms of reports, but I would submit that is only partly correct.  I tell people that Telerik reports is a way for me to produce output that can be electronically distributed or printed.  While that is a definition of a report, I think it can go a bit further.

If you think about PDF forms and what they are, they are a report that allows the user to add additional information and send back to the customer.  I do realize that some features of PDF forms allow for scripting that can automatically submit, and there is a lot of other capabilities that moves PDF forms outside the realm of basic report generation. That being said, the ability to set a parameter in a report whereas the fields are replaced with basic text input PDF fields would be a huge advantage for Telerik.  I could see them opening up the forms generation market for this product.

While I have no input into your roadmap and, as a former Product Architect for a software development firm, I fully understand scope creep and keeping product focus, I would love to see:
1) a parameter export to PDF that converts the fields (everything that has a Fields.XXXX keyword somewhere in the value property) to PDF form text fields without adding data.  I would set the length the same way you set the horizontal length of the field on the report.
2) a parameter on a field item that says this field cannot be converted into a form field and must have data.
3) a parameter on reports indicating that when generating PDF form fields, that X number of rows are generated for the detail section.
4) if a field value is too complex or if the report is too complex, I would just fail over to a blank value.
I realize there are a lot of capabilities in PDF forms, but I tried to keep my wish list confined to the basics that would allow for easy additions to support advanced capabilities post report generation.

All this being said, I have communicated to my customers that Telerik is not going to support PDF form fields and we have an upcoming meeting to discuss this requirement.  I have a lot of resources, time and money invested in the development of Telerik reports and it is a concern that I may have to remove Telerik reports from our solutions because of a need to support this PDF capability.  We have reports on multiple different platforms and I feel that Telerik Reports is one of the best in terms of use on many different styles of applications. But since I am a firm believer in using as few technology vendors as possible (and only want a single reporting solution), I am concerned about having to re-architect our solution reporting infrastructure to remove Telerik reports.

if you can provide a default resource file of report designer, and provide the same name convention rule of the resource file, then we can translate it by ourselves.

DocumentMap is using the order of report structure to create the tree. For the moment, the only way to change this order is using "Bring To Front/Send To Back" in report designer, which is badly named in this case, and awkward to use.

You should:
-add Bring Forward/Bring Backward functions
-document in DocumentMap help section that theses functions will also change the order in the report structure.

Ideally, a move up/down in report explorer view would be even better (and more intuitive).

Can the Telerik Reporting libraries be available for install as a NuGet package that can be hosted on a local NuGet server?

Hosting on the public NuGet server would be even better, but I would imagine that would be harder to get approved.

The report Parameter as of now can only be Boolean, Date, Int, Float or String. It would be great to be able to have a Guid parameter. This is particularly useful when passing a Guid to a child report parameter that in turns needs to be a Guid again to be run in the query. As of today we must convert the Master Guid to String to be able to assign it to a parameter then the child report reconverts it into a Guid to be passed to the query

Please add a new ZoomMode to stretch the report to the viewer's visible area 

In the development of a form which prints over multiple pages, the only way to ensure page breaks occur where desired is to use multiple Groups, with only the Group Headers Visible.
It would be more logical to be able to insert multiple Detail Sections, with each on their on page. Another option may be to insert a page break within the Detail Section.

It would be great to be able to plot a "Heat Map" style report

Add the ability to control the distance between the Image and the Text for a Check Box & Radio Box. A space may be used but this does not work where the text wraps to another line and does not give the required level of control.

Currently, there is no natural way to disable picturebox errors. Sometimes we do not care to know that the image wasn't found, especially when the error shown severely damages the look of the report, stretching and pushing things out of the way. The image URL may be built via parameters, pointing to a large folder where photos of a given employee may or may not exist. It took multiple unhelpful support tickets, many headaches and days of research to finally find an obscure post by a private individual with an undocumented custom solution that worked. 

freeze certain columns in a table when we scroll right and left in Telerik Report and the same should be applicable when we do export to excel

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..

We need the ability to automatically adapt report layout after its page size chages using report elements docking, anchoring etc. functionality.

This will allow us to reuse report templates for different printer paper sizes without making specific report for each paper size.

We do not have knowledge of internal report layout composition so a layout changes cannot be done with custom code, but need to be specified in reports directly.

 

Thank you

 

Marek Istvanek

It will be good to have a section similar to Page Header/Footer that can be placed on the left/right of each Page.

Feature Request - Show email sent / error notification using the report viewers built-in notification system. 

It would be nice to have an option to have a message shown when the email with the report is sent or if there was an error sending.
Right now when you hit email and send the user does not know if it was successful or not. Being async is nice but I have noticed that it could take a few seconds to complete and if the user navigates away from the report viewer during this time the report has the possibility of not sending. Either way right now the user has no definitive method of knowing if the email was sent or not.

 

 

As part of our security best practices, we need all components that we use to be Code Signed using SHA256.

Add context menu commands and improve the user experience for editing Crosstab, Table, and List items.

When there are both ASCII characters and non-ASCII characters (such as Chinese) in the text box, the position of line wrapping in Linux Docker is incorrect. Some of the data get lost.

More information can be found in the forum thread TextBox's line wrap position is incorrect in docker.

Besides the filtering of a table/report group, which allows columns/rows omission, I need to be able to dynamically change the value of the Visibility property of a table or report group, so that the content of individual rows and/or columns can be easily hidden or displayed.