Pending Review
Last Updated: 18 Nov 2026 15:49 by ADMIN

Add support for strip lines in graph/chart components, similar to the functionality available in RDLC/SSRS. Strip lines are visual reference elements associated with an axis that allow users to highlight specific values, thresholds, or ranges directly within the chart.

Typical use cases include:

- Displaying target or threshold values (for example, SLA targets, budget limits, warning levels).
- Highlighting acceptable, critical, or goal ranges using shaded bands.
- Emphasizing recurring intervals or important regions of the chart.
- Improving data interpretation by providing visual context without requiring additional data series.

A strip line can be rendered as:

- A horizontal or vertical reference line at a specified axis value.
- A shaded band spanning a configurable value range.
- An optional labeled element with customizable appearance (color, border, opacity, text).

Currently, similar scenarios require workarounds such as adding constant-value series or annotations. Native strip line support would provide a simpler, more intuitive, and more flexible way to visualize thresholds and ranges in charts.

Completed
Last Updated: 18 Nov 2026 15:34 by ADMIN
Release 2026 Q4 (Nov)

I use the Verdana font in my report titles. In the desktop designer and PDF documents, the text appears as expected.

In HTML5 and Blazor Report Viewers, though, the characters like 'p', 'q ', and 'y' appear cut off:

 

Unplanned
Last Updated: 18 Nov 2026 08:30 by ADMIN
Scheduled for 2026 Q4 (Dec)
After a large report is rendered, subsequent report renders in the same process may produce excessive memory allocations and become significantly slower. The behavior is caused by large StringBuilder instances being retained and reused from the shared pool.
In Development
Last Updated: 17 Nov 2026 17:03 by ADMIN
Scheduled for 2026 Q4 (Dec)
The https://www.telerik.com/products/reporting/documentation/designing-reports/json-report-definitions/json-schema article mentions the Telerik.Reporting.Schema package, but it is not available anywhere - neither on nuget.org, nor on the Downloads page of my Telerik account. Please address this.
In Development
Last Updated: 17 Nov 2026 11:41 by ADMIN

We have an application that is generating very large reports in "Print Preview" mode.

When the first page of the report is generated the Export button gets enabled. If the user does not wait for the report to be fully generated, and clicks the Export button, it doesn't do anything. We have also seen the application crash after clicking the Export button while the pages are loading.

In Development
Last Updated: 16 Nov 2026 13:47 by ADMIN
Scheduled for 2026 Q4 (Dec)

When using Kendo UI for jQuery 2026.4.1111, or the other Kendo suites that use it internally such as Telerik UI for MVC, AJAX, and so on,  the report viewer does not render. Instead, on the page, the exception "Error loading the report viewer's templates" is shown.

The issue occurs because the report viewer templates tries to load an icon with the name of "x-outline", which in the latest kendo release has been renamed to "x-circle".

The workarounds are to either use an older Kendo version such as 2026.3.1015, or to update the template of the report viewer to use the correctly named icon, and load the edited template - Telerik Reporting Displaying Reports Web Application HTML5 Report Viewer Customizing Styling and Appearance Providing Custom Templates - Telerik Reporting.

Unplanned
Last Updated: 16 Nov 2026 09:43 by ADMIN
Scheduled for 2026 Q4 (Dec)

Almost any object can be set to grow (CanGrow = True). Which makes the object grow if the text is too long.

I believe you need a function for making the text fit inside the object.

“ShrinkToFit = True”

This would shrink the text so that it fits inside the object. So if the font size is 20 and a long text wouldn’t fit inside the object, the font size would shrink until it fits.

Today we need to set several conditional formatting rules for this and it’s far from perfect. 

Completed
Last Updated: 16 Nov 2026 08:39 by ADMIN
Release 2026 Q4 (Nov)
Created by: Chirag
Comments: 6
Category: Reporting
Type: Feature Request
32
It would be good a maintain the scroll position on the parent page while navigating back from a drill-through report (using the back button of the report viewer) specially if the parent page contains a vertical scrollbar. This would enhance the user experience and eliminate the need to scroll back to the original position.
Unplanned
Last Updated: 13 Nov 2026 16:15 by ADMIN
Scheduled for 2026 Q4 (Dec)

We have spotted that PInvoke is now marked as deprecated (this applies even to the latest 0.7.124 version). In the description of the PInvoke.User32 NuGet package, it is mentioned that Microsoft.Windows.CsWin32 should be used instead:

Please consider replacing the deprecated package.

Unplanned
Last Updated: 13 Nov 2026 16:06 by ADMIN
Scheduled for 2026 Q4 (Dec)
Currently, Telerik Report Designer cannot export the style heading level to the tag structure in the generated PDF. It exports the headings, yes, but only as a paragraph tag. This request would require that a Heading Level (e.g., Heading 1, Heading 2, Heading 3 ) field be added to the Properties panel such that a text box could be tagged as H1, H2, H3, etc.  According to accessibility guidelines, PDF/UA-1, WCAG 2.1 and 508, the tag tree needs to contain a logical reading order and tag structure. Heading Levels are essential to that. There may be only one H1 - usually reserved for the document title, then major sections get H2, subsections, H3, etc. Can this be done?
Unplanned
Last Updated: 13 Nov 2026 16:05 by ADMIN
Scheduled for 2026 Q4 (Dec)

I am using the Standalone Report Designer for .NET to open a code-based report from an application that was migrated from .NET Framework. Before the migration, function calls defined in the designer.cs file were preserved and evaluated at runtime as expected. However, after migrating to the code-based reports functionality supported by the Standalone Report Designer for .NET, these function calls are evaluated immediately during the report import process, and the resulting values are then serialized and stored in the report definition.

It would be nice if the function calls were preserved in the imported report, allowing them to be evaluated later at runtime, as their return values may change depending on the execution context.

Unplanned
Last Updated: 13 Nov 2026 16:05 by ADMIN
Scheduled for 2026 Q4 (Dec)
Created by: Pascal
Comments: 1
Category: Reporting
Type: Feature Request
1
The fonts defined in the fontLibrary element are discovered once, lazily on first use, and are cached for the process lifetime. Fonts added to the configured directories afterward are not picked up automatically —  a restart of the application is needed.
As we install fonts regularly and don't want to restart/redeploy everytime we install a new font we propose a new api to clear the cache.
A new method Telerik.Reporting.Fonts.RefreshCache would solve this problem and improve the experience of using the Telerik Reporting library.
Unplanned
Last Updated: 13 Nov 2026 16:00 by ADMIN
Scheduled for 2026 Q4 (Dec)

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: 13 Nov 2026 16:00 by ADMIN
Scheduled for 2026 Q4 (Dec)
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.
Unplanned
Last Updated: 13 Nov 2026 16:00 by ADMIN
Scheduled for 2026 Q4 (Dec)

The bug has two requirements for occurring:

  • The system locale(culture) must use a comma as the decimal separator
  • The report must contain at least one item, which takes the full available width of the report sections. Or an item may be docked to a section, which results in the same width as that of the section.

When those two conditions are met, the report will fail to render, and an error message stating that one of the numeric values in the report cannot be parsed. For example, the message may look like this:

One or more errors occurred. (The numeric portion of 170.01mm cannot be parsed as a unit of type Mm.)

To avoid the issue, slightly decrease the width of the item so that it does not occupy the full width of the report section. If Docking is used, disable it, or wrap the docked item in a smaller container.

Alternatively, a culture with a dot-based decimal separator may be used.

In Development
Last Updated: 13 Nov 2026 15:59 by ADMIN
Scheduled for 2026 Q4 (Dec)

Currently, when you set SplitWorksheetOnPageBreak to True, the Excel Sheet name is formed from the DocumentName or ReportName and the number of the page.

It would be very helpful if the report authors can manipulate these names with Expressions.

In Development
Last Updated: 13 Nov 2026 15:51 by ADMIN
Scheduled for 2026 Q4 (Dec)
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: 13 Nov 2026 10:45 by Jenifer

I installed Reporting on my Windows without a database server. I chose to install with the examples so I can later provide a valid connection string for them.

Here is the connection string from the XML configuration that breaks the Standalone Report Designer applications:

<connectionStrings>
        <clear/>
        <add name="Telerik.Reporting.Examples.CSharp.Properties.Settings.TelerikConnectionString" connectionString="Data Source="No Local Servers Found!";Initial Catalog=AdventureWorks;Integrated Security=True;Password=" providerName="System.Data.SqlClient"/>
</connectionStrings>

Note the quotation marks inside the DataSource value that make the XML invalid.

Previously, the same scenario resulted in the following connection string that didn't break the XML structure:

<connectionStrings>
    <add name="Telerik.Reporting.Examples.CSharp.Properties.Settings.TelerikConnectionString"
        connectionString="Data Source=No Local Servers Found!;Initial Catalog=AdventureWorks;Integrated Security=SSPI"
        providerName="System.Data.SqlClient" />
</connectionStrings>

Currently, to start the designers, I must fix the configuration files manually or install the Reporting without examples.

Unplanned
Last Updated: 13 Nov 2026 10:22 by Georgy
When an HTML5-based report viewer is in Fit Page Width scale mode, the page keeps resizing in a loop at certain viewer sizes. This happens when the page is almost exactly as wide as the available space, so showing or hiding the vertical scrollbar changes the content width.
Completed
Last Updated: 12 Nov 2026 13:43 by ADMIN
Release 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.
1 2 3 4 5 6