As soon as I reference a .NET 10 assembly containing models, there is a null reference exception that does not appear in EventViewer or Fusion logging at the opening of the Standalone Report Designer for .NET.

Here is a link to a muted video demonstrating how adding assembly references using the UI successfully adds the custom assembly to the designer, as well as the bug when removing the assembly version.

I have a crosstab with a dynamic number of columns (time periods) that can exceed 15-20 columns. When exporting the report to PDF in A4 landscape format, excess columns are truncated and never printed on additional horizontal pages.

The issue is related to the Crosstab property 'RowHeadersPrintOnEveryPage'. When set to True, it places additional row headers on each page when using physical pagination. I suspect these additional headers are not taken into account when calculating the necessary page area, hence the final part of the Crosstab is skipped.

Consider adding support for a ToC in the XLSX rendering format. Depending on the `SplitWorksheetOnPageBreak` device info setting, I expect the hyperlinks to either lead to a section within the same worksheet or to a different worksheet.

The Table of Contents(TOC) section is displayed at the bottom of the document map, despite appearing at the beginning of the rendered report itself. This can be confusing for the end-user.

We see a console error when navigating away from the Blazor Native report viewer page. The page that contains the breadcrumb and the viewer has query-supplied parameters.

Using the text-indent CSS setting results in part of the text on the first line being cut off:

 

I am using the obsolete `Telerik.Reporting.Chart` type for a chart in a report. When I attempt to preview the report, an error is thrown:

The type "Telerik.Reporting.Chart" contained in assembly "Telerik.Reporting, Version=19.2.25.1001, Culture=neutral, PublicKeyToken=a9d7983dfcc261be" cannot be loaded.
To help improve the application's security, the reporting engine prevents loading types that are not essentially needed or listed as trusted by the user. If you consider particular types or assemblies as trusted include them in the corresponding TypeReferences or AssemblyReferences element of the 'Telerik.Reporting' configuration section in the application's configuration file.

When using the Native Blazor report viewer with the latest version of Telerik UI for Blazor (12.0.0), the following exception is thrown:

Unhandled exception rendering component: Object of type 'Telerik.Blazor.Components.TelerikToolBar' does not have a property matching the name 'Adaptive'.

We have some issues with cut off texts on our PDF reports. It only happens rarely and only with some fonts.

 

TSE note: This is an investigation item for tracking purposes. The actual font is included in the private GitHub issue linked to this item.

Currently, there is an MCP server that allows for integrating and developing report viewers, report designers, and Reporting REST APIs through Copilot. Consider allowing end users without Telerik Reporting experience to also build reports using AI.

 

I set the OwnerPassword and UserPassword device settings when exporting to PDF, and when I try to open such a PDF on a Mac with Safari, Preview, etc. the document appears blank after providing the password.

In MSSQL, you may use syntax like 'StoredProcedureName;1' to indicate stored procedure versioning, but it is not yet supported by Telerik Reporting.

I use such syntax and need to remove the version to make this work in Telerik Reporting.

It would be great if you also added support for versioning in MSSQL stored procedures.

Currently, the Graph Axes seem to be drawn after the Series, so when they overlap, the corresponding part of the Series lines is not visible.

If you add transparency to a Graph line, for example, the Y-axis, with an alpha value: '150, 255, 255, 192', it is respected in the Standalone Report Designer, where the rendering format is Image.

In the Web Report Designer and in the HTML5 Report Viewer preview, the alpha value is ignored, and the color is rendered as '255, 255, 192', which removes the transparency.

The Initialize method in ReportViewer.cs is called from both the OnLoaded and OnApplyTemplate methods, which in turn calls the AttachModelEventHandlers method. This leads to it adding the event handlers to the model twice every time it is loaded. The DetachModelEventHandlers is only called once (in the OnUnloaded method), so if you keep unloading and reloading the control, it adds 2 event handler invocations but removes only one. This means each one is called at least twice (if you have only loaded the control once), then 3, 4, 5, etc times if you keep unloading and reloading it.

I've worked around this by adding code to my wrapper class to prune the duplicated handlers for now, but this needs fixing in the base code.

I need to be able to save the report as a PDF/A-2u-compliant document. I hope you will introduce this functionality soon in Telerik Reporting, as it is already available in Telerik Document Processing.

Hi Team
We purchased a reporting component and need to use a table of contents for our reports
The table of contents does not support right to left - for Hebrew/Arabic language
This is really problematic and seems to me a basic need that should be included in the service
We expect a solution soon
Thank you

I have a case where I need to allow the hyphen (-), but currently I don't have a way to remove this character from the rule to add the FormulaPrefix.

I would like to request the addition of FormulaPrefixCharacters.

I'm using the WinUI Report Viewer in my .NET 8 WinUI3 desktop application.  All my reports initially render and display correctly, however, when the user clicks on the Print Preview button to switch to the print preview view, it causes my app to crash. This only occurs when using Versions 19.1.25.521 and above of the Telerik.ReportViewer.WinUI package. If I roll the NuGet back down to versions 19.0.25.313 and below, my application happily switches between interactive and print preview view without error.

Interestingly, if I force the Report Viewer to start in print preview view (with ViewMode="PrintPreview" in the xaml), it displays without error (though the toolbar print preview button is not showing as being toggled).  I can then also switch to interactive mode once without error by toggling the print preview button. However, if I then attempt to switch back to the print preview mode, it again crashes.

I have a .NET project. I tried to add a CS-based report to it using the Visual Studio item template. However, when I opened it, I encountered an error message, which wasn't helpful.

After reaching out to the technical support, I was told that the Visual Studio Report Designer was not supported in .NET projects, and the alternative was either to open the CS-based report through the Standalone Report Designer or use TRDP reports (recommended for new reports) instead.

It would be nice if there were some warning about this, as it would save me some time and confusion, as at first, when I encountered the error message, I took the assumption that something was corrupted with my project.