Unplanned
Last Updated: 12 Oct 2026 14:29 by ADMIN
Created by: Xorcist
Comments: 1
Category: Reporting
Type: Feature Request
1

Is it possible to get descriptive information exposed for the ReportsControllerBase swagger endpoints? do they exist?

Notice how the About and files endpoints have information next to them:

Like-wise how the files endpoint has descriptive parameters:


Unplanned
Last Updated: 12 Oct 2026 14:12 by ADMIN

I run an ASP.NET Core application that has the functionality to export reports into PDFs in an Azure environment.

There is no way to install additional fonts on Azure so I provide the fonts used in my reports via the "privateFonts" element of the Reporting configuration.

This works for the most part, the font is embedded in the produced PDFs but if I have a textbox with a large text, the text may be cut off when using the Skia engine.

I tested running my application in Docker, I copied the needed fonts in the usr/share/fonts directory of the Docker Linux container, and tried exporting again.

When exporting from Docker, with the fonts installed in the container, the text is not cut off. It seems that there is an issue when the fonts are provided as private fonts.

Unplanned
Last Updated: 12 Oct 2026 14:04 by ADMIN

Hi Telerik Team,

We are experiencing an issue related to tooltips in PDF exports from Telerik Reporting.
When we enable tooltips using the ViewerRenderToolTips setting both at the report level and through the device info in the report service, tooltips are appearing in the exported PDF—but they are being rendered as text annotations, not as normal tooltips.

Issue:
In the resulting PDF, tooltips are rendered as Text Annotations, which:

1.Appear as popups or sticky notes on mouse hover/click
2.Are not the standard tooltip experience expected by users
3.May affect accessibility compliance and user readability

Expected Behavior:
Tooltips should appear as standard PDF tooltips (like browser-style hover text) instead of annotations.

Attachments:
Sample Telerik Report (.trdp)
Generated PDF output showing the issue

Please advise if this is expected behavior or a bug, and whether there's a way to control the tooltip rendering to match typical PDF tooltip behavior (or to make them more accessible).

Thanks,
Pramod
Unplanned
Last Updated: 12 Oct 2026 13:41 by ADMIN

ADA Accessibility is a priority for our customers, so we are aiming to ensure logical tabbing order for keyboard users.

I've noticed that the RowHeadersPrintOnEveryPage attribute, while very useful for creating more readable PDF exports, seems to result in some strange screen reader behavior when set to True.

The first problem is with the strange tabbing order in the live environment. The second column header is the first to receive focus, followed by the remaining column headers, then the data fields under the first column receive focus in a vertical list, until finally the first column header receives focus. Without the default RowHeadersPrintOnEveryPage setting (False), the first column header is the first to receive focus, which is expected. 

In addition to the wrong tabbing order, the RowHeaderPrintOnEveryPage causes the screen reader to announce the incorrect column associated with a particular cell. I use the Windows Narrator. Other screen readers may result in slightly different behavior. 

Unplanned
Last Updated: 12 Oct 2026 13:37 by ADMIN
Hi,

Currently, if Thread.CurrentThread.CurrentCulture set to tr-TR (can be also reproduced with az-AZ and maybe some other cultures) some tags are ignored in HtmlTextBox, but they work if typed in UpperCase. This can be reproduced with any supported tag which contains letter "i" like "div" or "li".

For example, we have two ol list but one with LI and the other one with li tags:

<ol>
  <LI>first</LI>
  <LI>second</LI>
</ol>

<ol>
  <li>first</li>
  <li>second</li>
</ol>

This is how it is rendered in PDF:


When the current thread culture is set to Turkish (tr-TR), the lowercase and uppercase conversion rules differ from English — especially for the letter "i".

  • In Turkish:

    • "i".ToUpper() → İ (with a dot)

    • "I".ToLower() → ı (dotless i)

Our assumption that the Telerik HtmlTextBox internally parses and maps HTML tags by converting them to uppercase. When the Turkish culture is active, this conversion causes tag names to break, which is not a valid tag, so ordered lists fail to render.

Best regards,
Denis

Unplanned
Last Updated: 12 Oct 2026 13:24 by ADMIN

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.

Unplanned
Last Updated: 12 Oct 2026 12:37 by ADMIN

I want to set the Table ColumnWidth to a particular value in the Properties of the Web Report Designer. There is no property ColumnWidth as in the Desktop designers, and I tried to set the Size.Width, which is available.

When I increased the Width from the Properties, in design time, there is no change in the column width, only dashed borders indicating the new size when selecting the corresponding TextBoxes. In runtime, though, the new size is respected.

The inconsistency repeats even when I open the saved report in another browser or through another application, hence this is not a caching issue.

In Development
Last Updated: 09 Oct 2026 10:02 by ADMIN

Currently, when I create a report with the Standalone Designer and localize it, I can preview it only with the language of the machine where I run the designer.

It would be very helpful to have the option to select one of the languages I have set up during localization when previewing.

Completed
Last Updated: 09 Oct 2026 09:38 by ADMIN
Release 2026 Q3 (Oct)
Created by: Milen, Product Manager in DX
Comments: 1
Category: Reporting
Type: Feature Request
4
As a user of the Web report designer,
I want to be able to localize my reports for particular languages/cultures,
So they may be consumed by diverse end-users.
Completed
Last Updated: 09 Oct 2026 08:23 by ADMIN
Release 2026 Q3 (Oct)

Currently, if I want to see what the device info settings for an extension like the PDF are, I need to open the documentation - Telerik Reporting Configuring the Output Formats PDF Device Information Settings - Telerik Reporting, then copy the setting that I wish to use in my code.

It would be easier and safer if the device information settings for each format were exposed as a public enum/class. On that note, it would also be easier if the available formats were exposed as well, instead of manually typing them. For example:

public static classTelerikDeviceInfoSetting
{
    public static class PDF
    {
        public const string DOCUMENTTITLE = "DocumentTitle";
        public const string DOCUMENTAUTHOR = "DocumentAuthor";
        public const string DOCUMENTSUBJECT = "DocumentSubject";
        public const string DOCUMENTPRODUCER = "DocumentProducer";
        public const string DOCUMENTCREATOR = "DocumentCreator";
    }

    public static class XLSX
    {
        public const string USENATIVEPAGEHEADER = "UseNativePageHeader";
        public const string USENATIVEPAGEFOOTER = "UseNativePageFooter";
        public const string SHOWGRIDLINES = "ShowGridlines";
    }
}

public static class TelerikRenderingExtension

{

public const string PDF = "PDF";

public const string XLSX = "XLSX";

}

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

When I enable accessibility in my reports, the final PDF document becomes 20+ times bigger than without accessibility. The reports contain large amounts of data and result in 2000+ pages.

I need the images in my reports (usually only one logo) to have alternative text, so the screen readers can describe them. To achieve this, currently I have to enable accessibility for the entire report, hence the huge final documents.

It would be very useful for my scenario to add alternative text to the PictureBox without declaring the entire report as accessible.

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:30 by ADMIN
Release 2026 Q3 (Oct)
Created by: Jacob Overgaard
Comments: 2
Category: Reporting
Type: Feature Request
2

When generating PDF/UA files, we need to have special objects that are read by an internal system but ignored by screen readers. This cannot be achieved with the existing functionality.

It would be beneficial if we could configure reports so that specific objects inside the generated document are ignored by screen readers. For example, by setting a special value to the AccessibleRole property of a text box. 

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

In the Q3 2026 release, Telerik Reporting updated the kendo font icons used by the web report viewers.  Those icons are loaded alongside the report viewers and are not scoped to them, so they override the icons for elements outside the viewers.

For example, the Telerik UI for AJAX product is currently using kendo font icon subset that is older, so when I load the HTML5/HTML% WebForms report viewer on the page, AJAX's icons are overridden and incorrect.

Migrate the web reports viewers to use Kendo SVG Icons instead of the current font icons implementation, as they allow for better flexibility and render more nicely on the page, and will avoid the issue with overriding font icons when the viewers are used with other Telerik products.

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: Jim
Comments: 9
Category: Reporting
Type: Feature Request
9

Hello,

I see from support threads that Telerik really resists any changes to their concept of CSV rendering.  And I also understand the reasoning in not changing any default behavior due to its potentially unwanted effect on established customers.

That said, I wonder if the ability to exclude hidden objects (TextBoxes for example) has been proposed and is in the list of potential enhancements.  I wouldn't mind if it required a configuration setting like NoHiddenObjects = True where the default is False.

Has that been considered?