Unplanned
Last Updated: 23 May 2023 08:17 by Wolf

I need to know when one of my users has canceled the rendering of the report in order to update the UI accordingly.

Please consider firing a 'renderingCanceled' event when the above occurs or passing an additional parameter to the updateUi event to specify the rendering state.

Unplanned
Last Updated: 18 Feb 2025 15:41 by ADMIN
Allow order of report tabs to be re-arranged in Standalone Designer
Unplanned
Last Updated: 23 May 2023 14:39 by Dennis

There is a common error message received often after upgrading Telerik Reporting:

Unable to get report parameters. An error has occurred. Cannot read a document with the specified schema: http://schemas.telerik.com/reporting/2023/1.1. You might be using an older version of the product.

Obviously, I have a mismatch between the new report that I created and the deployed Reporting application. To create the report that is generating this error, I copied from an existing (and working) report.  Only changed the Stored Proc being called and a few field names.  Everything else is the same.

Except -- (OBVIOUSLY) -- when I saved the report -- the Designer changed the schema version. 

You need a way in the DESIGNER to display the schema version of the report. If these reports are TRDP then I don't see an obvious way of viewing the schema version of the report. I opened both reports in the designer and tried to find a way to view the schema versions of a working versus non-working report.  So that, I could determine which version of the designer that I need to drop back to (in order to create my copy of an existing report).

In your error message, you could easily provide additional detail but do not. You just say "product". Obviously, you know this but you don't report it to user.  For example, you could say -- "This report has schema version xx.xxx.xx but the Reporting Engine can only run reports of schema version yy.yyy.yy and below" or something to that affect.  Good error messages would go a long way to avoiding this frustration.

Unplanned
Last Updated: 15 May 2023 11:48 by Naim

If the CanGrow property of a TextBox/HtmlTextBox is set to True and Left and Right Anchoring is applied, the Height of the text box will be determined based on its design-time Width.

Thus, even if the actual final Width of the item is enough to fit its contents on a single row, the text box can have a larger than necessary Height.

Duplicated
Last Updated: 18 Jan 2024 15:39 by ADMIN

While some viewer options such as the pageMode, viewMode, etc. are already exposed and configurable through code, the parameters are not. This means that the viewer will always load the report with the default report parameter values which can troublesome.

For example, I need to be able to pass a JWT to a WebServiceDataSource inside my report and I use a report parameter for doing so. This works as expected when I use a simple report viewer but when the report is loaded by the Web Report Designer, it is not possible to pass a value from the front end where the designer is initialized.

Unplanned
Last Updated: 09 May 2023 07:50 by n/a

When rendering a report with a Graph on Linux, the labels of the Graph are not aligned properly.

For example, right-aligned labels are offset to the left depending on the content and length of each label.

Completed
Last Updated: 09 Jun 2023 14:35 by ADMIN
Release R2 2023
Created by: Maksym
Comments: 1
Category: Reporting
Type: Feature Request
4

Hi Team,

Currently, the Angular Report View doesn't appear to support the Ivy rendering. As of Angular 16 (released 4 days ago), the legacy rendering mode is fully removed. Which means the ReportViewer will no longer work in ng16 or later.

So this feature request is to move the ReportViewer to support Ivy (which will support Angular v9 to v16 and later).

Thank you,

Maks

Duplicated
Last Updated: 11 May 2023 15:36 by ADMIN
Created by: Micah
Comments: 1
Category: Reporting
Type: Feature Request
0
Provide a NPM package with the necessary types to make the React Report Viewer work correctly in .tsx files.
Unplanned
Last Updated: 03 May 2023 12:25 by Softwiz

I apply the operator TOP N (=5) to get only the first 5 records of a dataset sorted by a DateTime field. It sorts the data correctly as seen in the previewed report, but still returns all data records rather than the first 5 of them.

If I apply the TOP % operator, the dataset seems filtered as expected.

The workaround I have found is to apply second TOP N filtering with an empty expression as seen in the linked screenshot.

I have attached also a sample report demonstrating the issue and the workaround.

Completed
Last Updated: 07 Jun 2023 12:34 by ADMIN
Release R2 2023

When exporting a graph that has multiple line series and a category scale to CSV, the error "object reference not set to an instance of an object" is thrown.

More specifically, the issue occurs when one or more of the series do not have a corresponding non-null value for every category.

Duplicated
Last Updated: 28 Oct 2025 13:24 by ADMIN
When I set SkipBlankPage of the report to True and there is no significant content, the Html5 Viewer displays the server-side error message "The current data set presented in the report did not produce any significant content..." rather than the one specified in the viewer's string resources file noPageToDisplay property.
Completed
Last Updated: 14 Jul 2024 01:06 by Adam-ACS
Release R2 2023
In certain scenarios when a report has both a Table of Contents (TOC) and multiple nested SubReports, the calculated page numbers displayed in the TOC and the total page count are incorrect.
Completed
Last Updated: 07 Jun 2023 12:34 by ADMIN
Release R2 2023

Currently, the ReportDesignerControllerBase class does not enforce its own JsonSerializerSettings, rather it uses the ones set globally, on the application level. This could potentially lead to errors since the Web Report Designer requires the data to be serialized in camelCase. When PascalCase is used, certain functionalities get broken.

A way to avoid this would be to explicitly define JsonSerializerSetting in the ReportDesignerControllerBase class so that the Report Designer service does not break regardless of the setting defined on the application level.

Completed
Last Updated: 07 Jun 2023 12:34 by ADMIN
Release R2 2023
When using Kendo UI R1 2023 SP1 (version 2023.1.314), there is an unnecessary rectangle inside the splitter control for the report parameters area of the HTML5 Report Viewers.
Completed
Last Updated: 07 Jun 2023 12:34 by ADMIN
Release R2 2023
Created by: Petya
Comments: 0
Category: Reporting
Type: Bug Report
1
The Choropleth Map does not display correctly in Firefox, the issue is currently reproducible even with the Population Density Report Demo | Telerik Reporting.
Unplanned
Last Updated: 19 Apr 2023 11:47 by Dyan
Created by: Dyan
Comments: 0
Category: Reporting
Type: Bug Report
2

I have a Graph with a Legend with Position LeftCenter. I want the text of the legend to be Right-aligned.

However, neither the Series > LegendItem > Style > TextAlign gets respected, nor the GraphLegend > Style > TextAlign. the text is always left-aligned.

Unplanned
Last Updated: 21 Jul 2023 13:10 by Joshua

Currently the behavior of the Web Designer and Standalone Designer is different in regard to DateTime Report Parameters and its "Kind" property.
The Web Designer will assume the value is of Kind "Utc" and the Standalone Designer uses "Unspecified".

This recently became more of an issue since the newer PostgreSQL Provider versions are a lot more strict regarding the "Kind" property:
Npgsql: Timestamp rationalization and improvements

The consequence of this is not being able to use Sql parameters which will work in both the WebDesigner/WebViewer and the StandaloneDesigner:

To resolve this issue right now, one would need to resort to ugly workarounds:

  • Add a custom function which receives a DateTime "d" and DateTimeKind "k" value and returns the DateTime value "d" with the Kind set to "k"
    • Having to include a user dll to add that function seems overkill
    • You will need to change every report currently in use
  • Change the behavior of the WebDesigner to match the behavior of the Standalone Designer by using a custom IReportSourceResolver, manipulating currentParameterValues 
    • The Kind Property is set to "Unspecified" which is arguably the worst option to take between the three

 

To properly address this issue it needs to be possible to set the Kind property in the Viewer. Or at least the behavior between the WebDesigner and Standalone Designer should be the same.

Additionally/Alternativly it should be possible to set the target Kind in the Report Parameter.

With kind regards,
Dominik Rothert

Unplanned
Last Updated: 11 Oct 2023 14:38 by Wayne Hiller
Created by: Wayne Hiller
Comments: 2
Category: Reporting
Type: Bug Report
4
The Anchoring/Docking DropDownList editors are always disabled on all items in the reports when inside the Web Report Designer. The same reports work fine in the Standalone Report Designer.
Completed
Last Updated: 09 Jun 2023 14:41 by ADMIN
Release R2 2023

When Kendo version 2023.1.314 is used, the tooltips of the HTML5 Report Viewer and its wrappers flicker when the cursor hovers above them.

 

Telerik Reporting Version: 17.0.23.315

Declined
Last Updated: 07 Apr 2023 13:19 by ADMIN
Created by: Ronald
Comments: 1
Category: Reporting
Type: Bug Report
0

Report is working fine in local IIS but not in IIS server. See error details below.

Error creating report instance (Report = 'AttendanceTagging.trdp').
An error has occurred.
A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.