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";

}

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.

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. 

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.

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?

The Telerik.Reporting documentation mentions that the Telerik.Reporting.* libraries should be available on nuget.org with the most recent release. However, when I search for Telerik.Reporting in the NuGet Gallery, I am not able to find any Telerik.Reporting.* package. The other products we use (UI for WPF, Document Processing) seem to be available though.

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

Staff note: On the Reporting side, our initial goal was indeed to make Telerik Reporting available through nuget.org, alongside the rest of the Telerik product portfolio. However, we are currently investigating an issue that is preventing us from publishing the Telerik.Reporting packages to nuget.org, which has delayed their availability.

Please use this feedback item to subscribe to updates and receive a notification as soon as the Telerik.Reporting packages become available on nuget.org.

When I have multiple reports open in the Standalone Report Designer, I am not able to rearrange/reorder them.

Refer to the tab behavior in Visual Studio, where you can drag one tab and move it to be in front of another tab.

I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.

It would be very useful if we could copy/paste Report Parameters between reports.

Currently, logarithmic axes do not support the LabelStep and MajorStep properties, which makes it difficult to control label density and avoid visual clutter for larger data ranges.

Adding support for these settings (similar to numerical scales), or providing a way to conditionally hide axis labels, would significantly improve readability and axis customization.

If I open the expression dialog in the Web Report Designer and select one of the available functions, I will see a sample snippet in the third column below the expression area.

This column is not selectable, so I cannot copy the example and test it out. This example should be copyable, so that each function can be easily tested in the report designer.

When a report is saved in the Web Report Designer, a popup appears confirming that the report was successfully saved. However, it is visible for far too long and blocks users during this time.

This feature request is to add an 'ok', 'hide' or 'close' button to these types of popups so the user can dismiss it.

Thank you,

Shannon

Consider adding support for the `start` attribute of the `ol` element in HtmlTextBox. This would allow us to change the start counting:

The rendering extensions are currently loaded by the Telerik.Reporting.Processing.RenderingExtensionManager all at once in the main thread when the report processing starts. This is redundant because one report processing requires one rendering extension to be loaded.

It would be really useful if EntityDataSouce was updated to support Entity Framework Core contexts. EF Core depends on Standard 2.0 so can run on .NET Core or the full framework.

Currently, the GetDesignerResource endpoint of the Web Report Designer service is case-insensitive, which can lead to issues if the URL is made lowercase at some point, such as by a URL rewrite rule, or similar scenarios.

For example, the following reference to the Web Report Designer script will load return the file:

<script src="api/reportdesigner/designerresources/js/webReportDesigner"></script>

But if lowercase is used, for example, like this:

<script src="api/reportdesigner/designerresources/js/webreportdesigner"></script>

The request will return a 404(Not Found) response.