In Development
Last Updated: 09 Nov 2026 14:10 by ADMIN

Watermark Images with higher than the report rendering DPI are displayed clipped in PPTX rendering.

In PDF, preview of the designers and DOCX the same watermark is shown as expected.

If the DPI of the image is 96 as the default Windows machine DPI used for rendering, the Watermark is displayed correctly also in PPTX.

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.

In Development
Last Updated: 03 Nov 2026 12:39 by ADMIN

Scenarios:

  • Row groups with page breaks: Rows reference cell IDs that are not present on the current page, resulting in missing references.
  • Nested tables: Outer table rows reference IDs for cells containing inner tables, but those IDs are not rendered.
  • Plain tables and certain controls: These render correctly with no missing references.

Observed:

  • Violations of accessibility standards (WCAG 2.1 SC 1.3.1 / 4.1.2), with screen readers announcing empty rows and tools like axe-core reporting errors.

Expected:

  • 'aria-owns' lists only IDs that are rendered, and a row with no rendered cells is omitted (or rendered with role="presentation").
Unplanned
Last Updated: 30 Oct 2026 12:43 by ADMIN
Created by: Jonathan
Comments: 0
Category: Reporting
Type: Bug Report
3

Password-protected PDF documents generated with Telerik Reporting have blank pages when opened with an iPhone.

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: 30 Oct 2026 10:25 by ADMIN

Hello,

 it seems there is some glitch in blazor telerik web report designer. So its not possible, to use stored procedure with parameters as datasource

lets have input parmeter in SP, expecting "some value", how to configure it for report? Only person, which is designin report, puts the value in as constant.
@Typ=1 

1) - web report designer doesnt remember sql connection type(Choose data connection): Shared vs EMBEDED. Always fall to shared, when reopening report(but was configured as embeded).

2) - web repor designer, not applying DEFAULT "Configure design time parameters" VALUES, and also "Configure data source parameters". They are correctly stored in TRDP, they are visible in sql wizzard steps, but ALWAYS passed as NULL to the datasource when OPENING report. 
= so report is than messed up/or datasource invalid. 

**NOT BUG, ENHANCEMET: 3) - allow filtering in SQL datasource wizard "Stored procedure". Normally there is hundred of SP and its pain to pick one. OR allow to write SP directly

4) - when using SQL datasource, its not getting filed values correctly, this command is executed:
exec sp_executesql N' SET FMTONLY OFF; SET FMTONLY ON;exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;',N'@Typ nvarchar(1),@ID int',@Typ=N'1',@ID=30
in sql wizzard, there is command: "exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;"
how to solve that?
You are not ALWAYS allowed to modify SP. just consume as DATASOURCE, so its NOT VALID.
IF 1=0 BEGIN
        SET FMTONLY OFF
    END

iam unable to use version 1007-its not compatibile in project with telerik.blazor 15.1 (conflict in some skia or document proccesing nugets), but its not the case.

example:
Video demonstrating(reopened existing report), all described points + profiler result.

telerik sends - WRONG:
exec sp_executesql N' SET FMTONLY OFF; SET FMTONLY ON;exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;',N'@Typ nvarchar(4000),@ID int',@Typ=NULL,@ID=NULL
telerik SHOULD send:
exec sp_executesql N' SET FMTONLY OFF; SET FMTONLY ON;exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;',N'@Typ nvarchar(4000),@ID int',@Typ=N'1',@ID=30

TSQL demo procedure(one procedure for multiple sources - real world usage):
create PROCEDURE [dbo].[IMS_PRINT_GETSET]
@Typ INT,@ID INT
AS
BEGIN
  SET NOCOUNT ON;

  --!!TELERIK BUGFIX, but you are NOT ALWAYS permited to modify SP!!:
   IF 1=0 BEGIN
        SET FMTONLY OFF
    END  

IF @Typ=2 BEGIN
SELECT TOP 500 * FROM vTabOrders_active
RETURN
END

IF @Typ=1 BEGIN
SELECT TOP 500 ID,CisloZakazky,Nazev,Poradi FROM TabXYZ
RETURN
END

END

 

Thanks, even for some hotfix ideas.

    
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.

Completed
Last Updated: 23 Oct 2026 12:38 by ADMIN

The following screenshot demonstrates what the ToC looks like when rendered with Skia on Linux.

Below is the expected result. Rendered with GDI on Windows.

Unplanned
Last Updated: 23 Oct 2026 12:16 by Michal

If I create an SqlDataSource component through the wizard, and select the option to embed the connection in the report, and later open the SqlDataSource wizard for that component again, the wizard does not remember that the selected data option was "Embedded" and again defaults to a shared connection.

The wizard should remember the chosen option for the SqlDataSource component.

Unplanned
Last Updated: 20 Oct 2026 10:30 by Hendrik

Our Reportviewer is opened or displayed within a dialog, if i open the search the search dialog is moved to the far right side and is not visible directly.

We need to scroll to the search dialog to see it.

Unplanned
Last Updated: 13 Oct 2026 09:02 by Steven
When I have a multi-page report displayed in the HTML5 Report Viewer, and I scroll through the pages, sometimes the page number may not update for the current page that I am on.

This occurs most often with the first and last pages of the report. It seems that it might be an issue of the report viewer not switching the focus on current page. If I left-click in the area of the report currently displayed, the focus changes, and that seems to be enough to cause the code to update the page number input as well.
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: 13 Oct 2026 08:00 by ADMIN

All of my report parameters have their AutoRefresh setting set to False, and the parameters do not depend on each other, they are not cascading parameters. The parameters have available values.

If I change the value of one of the parameters, despite the above settings, all of the other parameters' data is re-retrieved(even if those parameters are not visible).

This causes issues because the "Preview" button is disabled until the parameters are refreshed, and makes the UX bad since if the connection is slow, the end-users will have to wait for the parameters area to refresh after changing any parameter value.  

Planned
Last Updated: 12 Oct 2026 15:41 by ADMIN
Created by: Andre
Comments: 2
Category: Reporting
Type: Bug Report
0

I'm using VS 2022, the demo reporting (Telerik_Reporting_2026_Q1_20_0_26_211). When using the "Telerik Report 2026 Q1 Wizard", I select the following

  • "Table Wizard"
  • Current Data Sources
  • Add New Data Sources
  • Select "Object Data Sources
  • I select my Assembly and data object.
  • I select the Data source Member

See attach file when I finish the wizard.

 

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:59 by ADMIN

Currently, when using External Stylesheets in the reports, the engine tries to first load the stylesheet as an embedded resource of the assembly. If it fails to load it from the assembly, a message is written to the trace along the lines of:

ESS: Attempt to load ExternalStyleSheet from EmbeddedResource from assembly Telerik.Reporting, Version=19.0.25.211 with resource name styles.xml is unsuccessful.

After this, the engine will try other ways to resolve the stylesheet such as from URI and if it succeeds, the report will render as expected.

This can create confusion because looking at the trace, one might think that there were errors with the rendering of the report because the stylesheet did not load but it was actually successfully loaded with one of the other approaches.

It would be better to write the errors to the trace only if the stylesheet does not load after all attempts.