Completed
Last Updated: 12 Nov 2026 13:43 by ADMIN
Release 2026 Q4 (Nov)

At the moment it's only possible to have your reports in old-fashioned projects.

It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).

Declined
Last Updated: 12 Nov 2026 13:42 by ADMIN
Scheduled for 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.
Completed
Last Updated: 12 Nov 2026 13:41 by ADMIN
Release 2026 Q4 (Nov)
I use databases with hundreds of stored procedures, and not being able to search by name is slowing me down.
Unplanned
Last Updated: 11 Nov 2026 12:15 by ADMIN

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: 11 Nov 2026 12:05 by ADMIN
Release 2026 Q3 (Oct)
Created by: Andrew
Comments: 5
Category: Reporting
Type: Feature Request
18

Images taken with a mobile device are sometimes displayed in PictureBox  rotated by 90, 180 or 270 degrees. The reason is that whenever a photo is taken, the device saves its current accelerometer orientation into a corresponding Exif tag with the image metadata, so this info is then read and taken into account by our Report Designer.

In Development
Last Updated: 10 Nov 2026 15:51 by ADMIN

When exporting to PDF from Telerik Report Designer the software creates a list of flat links for each TOC entry, but the links are separated in the structure from the TOC Label. While a good start, it would be better to use a main TOC tag under which each line in the TOC would receive a TOCI (Table of Contents Item) tag. Each TOCI would contain the label and link for the respective item. Attaching a few examples to assist.

<TOC> Table of contents element is an element that contains a structured list of items and labels identifying those items; has its own discrete hierarchy.
<TOCI> Table of contents item element is an item contained in a list associated with a table of contents element.

References:

https://www.hhs.gov/sites/default/files/pdf-tagging.pdf (page 29).

https://www.pdflib.com/pdf-knowledge-base/pdfua/the-pdfua-standard/ 

In Development
Last Updated: 10 Nov 2026 06:30 by ADMIN
Created by: Miguel
Comments: 2
Category: Reporting
Type: Feature Request
8

Currently, if the SkipBlankPages property is set to True and there is not any significant content in the report, the following message will be displayed in the designer and the viewer: The current data set presented in the report did not produce any significant content, so no pages were generated. If you need to see the whole report content, including blank pages, please contact the report author.

It would be nice if it can be localized in the viewers.
Unplanned
Last Updated: 09 Nov 2026 12:27 by Greg
Created by: Greg
Comments: 0
Category: Reporting
Type: Feature Request
1

Currently, like the FileStorage and the MsSqlServerSrorage, the Reporting service performs periodic clean ups of the cachec client assets in the RedisStorage.

Those assets are stored in keys, which do not have an expiration date, so the Reporting service is the one that is single-handedly responsible for deleting those keys.

This approach may work well for the other storages, but in terms of Redis, it leaves more to be desired. Some of the possible cons of this approach are that:

  1. Cleanup depends on traffic. Expired report data is removed only when a new viewer client registers. If the service stops getting viewer traffic, nothing it stored is ever removed.
  2. Upgrades leave data behind. The storage keys include the Telerik product version. After an upgrade, the service only looks at keys for the new version, so cleanup never reaches data written by the previous version. It stays in Redis for good, no matter how much traffic the service gets.

So whether Redis memory is ever reclaimed depends on viewer traffic and upgrade history. In a shared Redis cache, the leftover data builds up until the cache reaches its memory limit. Redis can't evict it, because standard eviction policies apply only to keys with an expiration. The cache then starts rejecting writes, which breaks every application using it.

A cache provider should guarantee its data expires on its own, without depending on later traffic or on cleanup code that knows about earlier versions.

Requested:
An expiration option on RedisStorage, with a sliding expiration refreshed on access. With that in place, Redis reclaims all storage on its own, including data from previous versions, regardless of viewer traffic.

In Development
Last Updated: 06 Nov 2026 14:06 by ADMIN

I am using the WPF report viewer; however, if I merge the theme resources directly to the report viewer, the search dialog clashes due to a missing "GlyphSearchStop" resource. If I apply them to the hosting window or on application level, the theme affects other controls as well.

Please allow for better control of this so that the resources only affect the viewer and its dialogs.

Completed
Last Updated: 30 Oct 2026 11:18 by ADMIN

Hello Team,

 

I will be great if the Telerik Reporting REST Service Core could support System.Text.Json serialization.

 

Best Regards,

Unplanned
Last Updated: 29 Oct 2026 10:34 by ADMIN
Created by: Pooja
Comments: 2
Category: Reporting
Type: Feature Request
2
Problem Statement
Our production users rely on Excel for downstream analysis (formulas, filtering, sorting, pivoting, and ad hoc insights).
Current Telerik Excel export is layout-first (pixel-perfect), which preserves visual report structure but introduces merged cells, blank spacing rows/columns, decorative styling, and images.

For large datasets, this causes:

significant post-processing overhead,
slower export pipelines,
less usable spreadsheets for analytical workflows.
Business Impact
High-volume production exports with large row counts.
Users need data-centric Excel files, not print-layout replicas.
We use the same .trdp for PDF and Excel:
PDF requires full visual fidelity.
Excel requires clean, tabular, analysis-ready output.
Lack of built-in data-only mode forces custom cleanup logic, increasing maintenance risk and runtime cost.
Requested Feature
Add a built-in Excel Data-Only export mode (similar to Crystal Reports behavior), optimized for analytics and scale.

Proposed behavior (Data-Only mode)
Export as a flat tabular dataset (header + detail rows).
Preserve native data types (date/number/boolean) and formulas where applicable.
Avoid layout artifacts:
no merged cells (unless explicitly requested),
no decorative blank rows/columns from visual layout,
optional suppression of images/shapes/charts.
Optional minimal formatting only:
keep number/date formats,
remove decorative styles/fills/borders by default.
Optional toggles:
include/exclude report header/footer rows,
include/exclude groups/subtotals,
include/exclude hidden/report-only visual items.
Keep worksheet gridlines visible by default in data-only mode.
Optimize for large datasets (streaming-friendly, reduced memory overhead).
Suggested API / Configuration (example)
DeviceInfo or rendering setting, e.g.:
ExcelMode=DataOnly (default remains Layout)
IncludeImages=false
IncludeDecorativeFormatting=false
PreserveDataTypes=true
PreserveNumberFormats=true
FlattenGroups=true
Why this matters
This feature would allow teams to:

use one .trdp for both PDF (visual) and Excel (data),
eliminate expensive post-processing,
improve performance and reliability at production scale,
deliver spreadsheets that are immediately usable for business analysis.
Current Workaround
We currently perform custom post-processing to rebuild a clean workbook from rendered output (strip layout effects, remove visual artifacts, compact rows/columns).
This is complex, expensive, and fragile compared to a native renderer capability.

Request
Please consider adding this feature to the Telerik Reporting roadmap, or provide an officially supported pattern to achieve equivalent data-only output for Excel at scale.
In Development
Last Updated: 27 Oct 2026 14:41 by ADMIN
Please add first-class support for CancellationToken in the ObjectDataSource pipeline.
In Development
Last Updated: 27 Oct 2026 11:00 by ADMIN
Scheduled for 2027 Q1
Created by: Casper
Comments: 9
Category: Reporting
Type: Feature Request
30

It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.

If you have a lot of graphs in your report then it is more convenient to change the color palette one place.

Unplanned
Last Updated: 21 Oct 2026 17:24 by ADMIN
Scheduled for 2026 Q4 (Nov)

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.

Completed
Last Updated: 13 Oct 2026 08:54 by ADMIN
Release 2025 Q2
Created by: admin
Comments: 1
Category: Reporting
Type: Feature Request
0

I have been forcing my webservice data source into a workable solution for making GraphQL requests. Right now in order for us to use GraphQL, we have to build out the request manually with a string such as the following:


{"query: "query GetSomeResult($input: Int!) {result {id name}}",
"variables": "{"input": @parameter}"
}

While this is a normal way to hand craft a GraphQL request, the issue I have is that it shouldn't need to be that hard. Also I get no intellisense or suggestion in regards to the data returning. This means that when I try to bind data to a text box, I have to visually validate that the [=Fields....] is actually correct by looking at the GraphQL query and at the code base. I would love to see the ability to to just say have a set of standard api technologies we could implement from such as GraphQL queries, GRPc queries, or any other contract style request. I would expect that the data source logic would be smart enough to parse the query (at least for GQL) and be able to provide reccomendations.

 

Also a major issue we have had is in being able to pass that data source to subReports, or dealing with any nested objects such as a user.address.addressLine1 would not be able to be found if address is a nested values like the following


user: {
  address: {
    addressLine1
  }
}

Unplanned
Last Updated: 13 Oct 2026 08:46 by ADMIN
Created by: KungFuBrad
Comments: 0
Category: Reporting
Type: Feature Request
1

The Telerik Reporting REST Service storage is automatically cleaned based on some configurable timeouts and hardcoded times. It requires an awaken service to be performed.

It would be very useful for the developer to be able to invoke manually the storage cleaning functionality either with code or through the service Web API.

Unplanned
Last Updated: 12 Oct 2026 15:19 by ADMIN
My Data Explorer shows "No Data Source" and empty field list, where prior to this, the fields were correctly listed.

I just recently updated to the latest reporting release  2025 Q1 in addition to updating to the newest Visual Studio Community 2022 (64-bit) - Current
Version 17.13.2

I installed the newest reporting update and updated my VS project.

I must have at least 50 different reports which I have previously designed and have been working fine.  The DataSource is set to the object exposing all the key fields using gets.  Works fine when running the program but after all the updates, all of a sudden I can see, in the designer, the fields in the fields list when editing an element value reference or in the the Data Explorer. 

Played with a sample element in the detail panel.  The form has the data source set correctly.  The toolbox also shows the reporting tools.  No go.

I verified the new reporting DLL is intact.

Same situation with all my reports.  All work fine running, just the designer interface is not working.

I even tried on another computer, also updated, and experienced the same problem.

Again, now all my reports don't show the list - something intrinsically has changed. with the setup and recognition of the DS.

Eric
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 13:45 by ADMIN
Currently, the auth token is not yet passed from the client to the service. For that reason, it would be nice if the bearer token can be passed with the Web Report Designer API Requests.
Unplanned
Last Updated: 09 Oct 2026 13:37 by ADMIN
Scheduled for 2026 Q4 (Nov)

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.

1 2 3 4 5 6