Is there a way to have the linear gauge display a value above the indicator?

Currently, adding custom HTTP request headers to the requests sent by the Blazor Report Viewer is not supported.   I would like this feature added so I may send an anti-forgery token and other values specific to my application in the header.   I'm not able to use the Blazor Report Viewer without this feature.

The Web Report Designer does not entirely comply with CSP standards, necessitating the use of the 'unsafe-eval' directive in our CSP policies to enable its functionality.

This directive poses significant security risks and undermines the purpose of implementing CSP in the first place. Please remove this requirement.

In the non-native angular report viewer we were using a customized template to change the order of the buttons and also to add custom buttons. We want to migrate to the Native Angular Report viewer but it lacks toolbar customization options. We need to be able to change the order and hide existing toolbar functions. Also we need the ability to define custom buttons with custom logic that executes when the button is pressed. 

I've tried to create a sub-class of the ReportingAngularViewerComponent and define a custom template for the toolbar, but the problem is that some of the core toolbar buttons (like zoom and pager) use custom local Telerik components that aren't exported from the ReportingAngularViewerModule, so I can't use those directly. 

It would be great if you can export all components used in the ReportingAngularViewerModule or provide an alternative way to customize the toolbar (may be similar to how you allow customization of the toolbar for the Editor control where users can define what toolbar commands are available, order them as they like and also define custom commands)

I export the same TRDP report that embeds a Bitmap image on Windows with GDI and on Linux Docker Container.

The result PDF file from the Linux environment is much bigger than the one generated on Windows.

SVG images with viewbox constraints may shrink vertically when there are no desired height/width settings even if the viewbox settings allow full rendering.

The approach explained in Custom Parameter Editors in the HTML5 Report Viewer is no longer working in Reporting version 2025 Q2 (19.1.25.521).

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

In a situation where the clients are entering formatted text into the system, none of the suggested work arounds for this item are acceptable.  Lacking this support, it is impossible to enter math expressions.

At runtime there is no way to easily access values from fields within the same row of a report using the WPF ReportViewer.  We have a requirement for our application where users may double-click a field and trigger the applicable editor to appear for quick access.  To enable this functionality, we need to retrieve values from within the same row as the field that was clicked.
While the TextBlock that was clicked may be accessed, there is no way to easily determine which controls within the control hierarchy belong to the same row as all page content is lumped into one canvas.  Searching for values by Name is not possible either as the name is not passed into the generated controls.
It is also not possible to create custom IAction implementations to handle this functionality either as they are not supported.

It would be nice to have 3D chart capabilities such as those found in the WPF ChartView or even the KendoUI charts.  The Telerik Reporting charts , although feature rich, are rather plain looking.

In general I quite like the Stand Alone Report Designer but one thing that is a bit painful is that the default height of new fields are way to big. About half the current height would be more appropriate. It wastes time to have to resize every field after adding it, and especially also having to also shrink the height of details section is you added a new field to it.
It would be ideal if you could add a configuration section where everyone can specify their own default values such as field height but page size would also be handy.

Thanks for a very handy product.

Regards

Edu

Please add support for PrivateFontCollection.  When the program is deployed to a location where it does not and cannot install system level fonts (for various reasons), it makes an application built with Telerik Reporting volatile.  

I submitted a ticket due to a conflict we ran into.  Telerik's  response was to install the fonts on the system.  However, the system controllers response is "this it why PrivateFontCollection was invented...you have the control to use any fonts you want."  As a result, a developer has to either give up Telerik (ex. for DevExpress which supports it) or change the deployment entirely which seems utterly ridiculous.  Due to some project constraints, we changed deployments in hopes of it being rectified.

This should also be supported in the standalone designer. 
There is currently a workaround via external assembly but this is not very elegant.

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

It would be useful to have tooltips to table header columns so we can explain what each column is showing.

Like the NeedDataSource, it will be nice if there was a PreRender event or similar.
So that way I could programmatically adjust elements based on the report parameters. Example: a column selection parameter (dropdown) that would then in the 'PreRender' remove or hide the columns from a table if the column name isn't in that multivalue parameter.

When a date is set as a report parameter in the HTML5 viewer, it formats the parameter as a JSON date using a timezone.  Where no time is specified this results in a time part added to the date when received at the server.  This is a problem, especially for browser in a negative offset zone, e.g. US, where upon the date goes to the previous day.  Please add support for parameter types of date, where no time is present and no conversion is done anywhere.

This is not a clone. It's a new request I had to add, since the old was closed with a technically fault answer. By technically fault I mean possible, but in real scenario unusuable.

F.e Jasper's SubReports have a property called DataSource. The sub-reporst uses this dataSOurce for rendering it content. The DataSource is always set on the Main report. Everything via designer, no need for coding. So I'd like to see such a possibility in telerik reports.

The suggested solution - with the bindings http://www.telerik.com/forums/how-to-bind-the-datasource-of-a-subreport-in-the-designer is technically wrong. It assumes that the child report knows at which level he resides inside the main report. The child report (or it's binding) should have not such info embedded. Let's see on an example. Let's have a dataset:
User.Address
User.PostalAddress
User.Wife.Address
User.Wife.PostalAddress

The dataset should be bound to the main report. The main report should have 2 sub-reports (address and postal addres). It can have an another sub-report (for wife data) which then would again have 2 sub-reports inside for addresses.

Using the technically wrong solution, the addresses for the main user should have a binding expr. like: =ReportItem.Parent.DataObject.xy and the wife's addresses have like: =ReportItem.Parent.Parent.DataObject.xy

There is a big problems with such a binding: the child must know the hierarchy of the data.

The technically clean solution is to have a dataset assigned to the main report. When adding a sub-report to the main report, via binding we should set the new data-source for the sub report. something like: MainReport.Data = dataSource. SubReportAddress = dataSourceOfTheCurrentReport.Address. SubReportWife = dataSourceOfTheCurrentReport.Wife and inside "wife report" the next sub-report for address address should have a binding again like: SubReportWifesAddress = dataSourceOfTheCurrentReport.Address

In the Configure Object Data Source Wizard, add a method of filtering the displayed Business Objects.
Where a large number of Business are display, scrolling can be painful to find the required one.