I am using Kendo UI R1 2023 SP2 (version 2023.1.425) themes. Telerik Reporting scripts and stylesheets have not been updated to reflect the latest changes of Kendo UI.

1st photo shows using bootstrap themes, 2nd photo shows using other themes. 

The value '姓名：' is rendered on two lines in a TextBox under Linux. The colon symbol at the end '：' appears on the second line no matter how wide is the TextBox. The colon character itself is a special Unicode Character “：” (U+FF1A).

There are other symbols that may be used instead of the colon to reproduce the issue in Linux rendering. Under Windows, the text is rendered as expected.

The fix to the bug TOC page numbers and total PageCount are incorrect in some scenarios provided in R2 2023 may have led to another bug, as when I render my report with TOC the total page count is not correct in PrintPreview, although the page number is correct.

For example, on the last page, I see page 126 out of 123.

Some SVG files are not rendered as expected when the PDF Rendering is used.

SVG opened in the browser:

SVG in rendered PDF file:

If you add two Bindings for the same property in the designer when you click OK, an error "Index must be within the bounds of the List. Parameter name: index" occurs and the Bindings are ignored.

I have a JsonDataSource that contains a Base64 string field I want to use in a PictureBox.

When I drag the field from the Data Explorer in the Report Designer, it creates a TextBox with the text content. When I run the report, there is an error "A generic error occurred in GDI+'.

Consider creating PictureBox when dragging a Base64 string instead of TextBox.

The following error is thrown during design time when a Barcode has a static value but one or more of its properties are bound to a report parameter through Bindings.

When actually previewing the report, the Barcode works as expected.

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.

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.

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.

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.

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.

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

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.

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.