Pending Review
Last Updated: 09 Oct 2026 16:08 by Petar

 

After upgrading Telerik.ReportViewer.BlazorNative to version 20.2.26.1007, rebuilding a project targeting .NET 9 or later fails with the following error:

Severity Code Description Project File Line Suppression State
Error (active) The asset 'C:\...\BlazorApp1\Debug\net10.0\compressed\14jp1i84hx-{0}-2x8nbomfaf-2x8nbomfaf.gz' can not be found at any of the searched locations 'C:\Users\<user>\.nuget\packages\telerik.reportviewer.blazornative\20.2.26.1007\staticwebassets\css\reporting-blazor-viewer.css.map' and 'C:\Users\<user>\.nuget\packages\telerik.reportviewer.blazornative\20.2.26.1007\staticwebassets\css\reporting-blazor-viewer.css.map'. BlazorApp1 C:\Program Files\dotnet\sdk\10.0.301\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets 276

-----------------------------------------------------------------------------------

The issue occurs because the NuGet package declares a CSS source map as a static web asset but does not include the corresponding file.

For the available workarounds, refer to the following Knowledge Base article: Missing CSS source map causes build failure in .NET 9 and later with Telerik.ReportViewer.BlazorNative 20.2.26.1007

Unplanned
Last Updated: 09 Oct 2026 13:42 by ADMIN
Scheduled for 2026 Q4 (Nov)

The data source preview in the web report designer does not show the full shape of the query. It has no horizontal scroll bar to verify the preview data for the entire projection.

Please consider addressing this.

In Development
Last Updated: 09 Oct 2026 13:42 by ADMIN
Scheduled for 2026 Q4 (Nov)

When a Table has a Group PageBreak that splits the Table into more than one page, the items below the table are rendered after the first part of the Table (after the first page break), rather than under the whole table.

The issue occurs in hard pagination: PrintPreview of the viewers, PDF, etc.

In Development
Last Updated: 09 Oct 2026 13:41 by ADMIN
Scheduled for 2026 Q4 (Nov)

The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.

The workaround is to avoid using the SQL DataSource wizard and edit the data source properties directly in the properties grid. You can check the attached silent video that demonstrates how to do so.
In Development
Last Updated: 09 Oct 2026 13:38 by ADMIN
Scheduled for 2026 Q4 (Nov)

I have a CS report that contains a SubReport with InstanceReportSource. I have it in a .NET 10 Classlibrary project.

I tried to edit this report as a coded report in SRD.NET. However, when I saved the report, in the 'designer.cs' file, the value assigned to the ReportSource of the SubReport was set to 'userreport1' that is not instantiated and throws.

Unplanned
Last Updated: 09 Oct 2026 13:38 by ADMIN
Scheduled for 2026 Q4 (Nov)
When content associated with a TOC entry is hidden, subsequent TOC page numbers may be offset by one page. In the attached sample, the issue occurs when a Group Footer containing the TOC entry is hidden and the TOC is close to spilling onto a second page.
In Development
Last Updated: 09 Oct 2026 13:38 by ADMIN
Scheduled for 2026 Q4 (Nov)
The Group Footer rows of my table are displayed thinner than the rest of the table rows in PDF rendering. However, they are designed the same as the Group Header Rows and the Detail rows.
Unplanned
Last Updated: 09 Oct 2026 13:36 by ADMIN
Scheduled for 2026 Q4 (Nov)

I have noticed that the performance of exporting reports has gotten worse in recent releases. After investigating, I found out that this is likely caused by the sheer size of the code in my projects.

To prove this, I created a simple application that renders a report to PDF programmatically. Then, I created 10 000+ dummy classes in the same project, and tried rendering the report again. The performance was noticeably impacted by this change.

 

Unplanned
Last Updated: 09 Oct 2026 13:35 by ADMIN
Scheduled for 2026 Q4 (Nov)

Currently, the desktop viewers don't allow adding custom headers to their requests to the service.
In HTML5-based web viewers, this is possible through the AjaxPrefilter event.

Completed
Last Updated: 08 Oct 2026 16:30 by ADMIN
Release 2026 Q3 (Oct)

The attached sample has a simple table with two row groups, and "header" rows created via "Insert Row -> Outside Group - above".
The groups have "keep together" set.

But despite this, the header rows render at the bottom of one page, with data rows on the following page. This should never happen, I can't think of any case it would be expected (it would be like having "Chapter 2" at the bottom of a page when the text for it starts on the next page). 

I also have a sample with just 1 row group, but with 2 detail rows, and the same thing happens. It only appears to work when there's just 1 row group and 1 detail row.

Completed
Last Updated: 08 Oct 2026 16:29 by ADMIN
Release 2026 Q3 (Oct)
The Telerik Reporting installer adds a copy of the legacy ASP.NET WebForms Report Viewer assembly(Telerik.ReportViewer.WebForms.dll) to the Global Assembly Cache (GAC).
Completed
Last Updated: 08 Oct 2026 16:29 by ADMIN
Release 2026 Q3 (Oct)
Created by: Nitin
Comments: 0
Category: Reporting
Type: Bug Report
1

I am using the HTML5 report viewer and seeing 4 errors in the WAVE tool, along with multiple alerts. See: https://wave.webaim.org/report#/https://demos.telerik.com/reporting/product-sales

Please consider addressing them.

Completed
Last Updated: 08 Oct 2026 16:29 by ADMIN
Release 2026 Q3 (Oct)
Telerik Reporting 2026 Q1 (20.0.26.211) fix to 'Paged report layout now supports repeatable table group headers/footers' is not working when embedded table (within a parent embedded table) spills on to the next page. The parent-embedded-table does not repeat in the header.

Completed
Last Updated: 08 Oct 2026 16:29 by ADMIN
Release 2026 Q3 (Oct)

I have localized a report with a Graph in the 'ar-SA' culture.

When exporting to PDF from the viewer, the report is generated as expected. In the Report Viewer's Preview, though, the Graph Legend and Labels are not correct:

I am using Native Blazor Report Viewer, but the problem also reproduces in the HTML5-based web viewers, with all the themes I have tested.

Completed
Last Updated: 08 Oct 2026 16:29 by ADMIN
Release 2026 Q3 (Oct)
When I configure a CsvDataSource through the wizard, leave "The CSV has headers" unset (generating dummy column names), then navigate back to select a different CSV file with actual headers and tick "The CSV has headers", the dummy columns from the first file persist instead of being replaced with the real headers from the new file.
Completed
Last Updated: 08 Oct 2026 16:28 by ADMIN
Release 2026 Q3 (Oct)
Created by: Maxim
Comments: 2
Category: Reporting
Type: Bug Report
6
I have a table in the Report Header and when I export to CSV format, the table does not appear in the document.
Unplanned
Last Updated: 05 Oct 2026 11:05 by ADMIN
Scheduled for 2026 Q3 (Oct)

When I render a report with Gujarati language text to PDF on Windows, the GDI graphics engine is used and the text is displayed properly.

When I render the same report with the Skia graphics engine, on Windows or Linux, the characters are misplaced or incorrectly drawn.

 

Duplicated
Last Updated: 30 Sep 2026 10:43 by ADMIN
DOCX export restarts the numbering on the second page for ordered lists.
Completed
Last Updated: 30 Sep 2026 10:38 by ADMIN
Release 2026 Q3

On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page. 

For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again.  The last two items should be numbered (4) and (5).

In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.

The attached file shows both these issues.

Completed
Last Updated: 24 Sep 2026 13:40 by ADMIN
Release 2025 Q4

When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.

The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.  

1 2 3 4 5 6