The Telerik.Reporting NuGet package brings unnecessary assemblies when used in .NET Framework projects due to the change to the nuspec in the Telerik Reporting - Progress® Telerik® Reporting R2 2022 SP1 (16.1.22.622) release.

Please add the possibility to merge cells in the Web Report Designer

As soon as I reference a .NET 10 assembly containing models, there is a null reference exception that does not appear in EventViewer or Fusion logging at the opening of the Standalone Report Designer for .NET.

Here is a link to a muted video demonstrating how adding assembly references using the UI successfully adds the custom assembly to the designer, as well as the bug when removing the assembly version.

I have a crosstab with a dynamic number of columns (time periods) that can exceed 15-20 columns. When exporting the report to PDF in A4 landscape format, excess columns are truncated and never printed on additional horizontal pages.

The issue is related to the Crosstab property 'RowHeadersPrintOnEveryPage'. When set to True, it places additional row headers on each page when using physical pagination. I suspect these additional headers are not taken into account when calculating the necessary page area, hence the final part of the Crosstab is skipped.

I have projects on .NET Core and I want to use the System.Text.Json serializer that is the new default, but reporting relies on Newtonsoft.Json.

---

ADMIN EDIT

There are two approaches that can be taken right now to solve this:

OPTION 1: define separate endpoints (services, projects) for the different tasks - they can still use the same database layer through a shared project, depending on the architecture you have. This would let you have separated services with the appropriate serializers without custom attributes and code (see below). For example, create a separate project for the reporting REST services.

OPTION 2: add some custom decoration on the endpoints so you can choose which serializer is used on each, you can find some examples here: https://stackoverflow.com/questions/59650907/how-to-configure-two-json-serializers-and-select-the-correct-one-based-on-the-ro - the point being to register a serializer depending on the endpoint based on your own code rather than let the framework put one in for all endpoints.

NOTE: This would be a breaking change.

---

Consider adding support for a ToC in the XLSX rendering format. Depending on the `SplitWorksheetOnPageBreak` device info setting, I expect the hyperlinks to either lead to a section within the same worksheet or to a different worksheet.

I have a string parameter with `autoRefresh` set to `true`. In the report viewer, it displays a textbox as a parameter editor. However, the report viewer refreshes on every "keydown" event, which can be frustrating for users. In the Standalone Report Designer, the report is refreshed only after the textbox is unfocused.

I have cascade parameters that depend on other parameters (check the Product Line Sales report for an example). I have set these parameters with `autoRefresh` of `false`. In the Standalone Report Designer, once I change the value of a parameter, the dependent parameter also changes automatically. However, this is not the case in the Native Angular report viewer.

I have 2 Date parameters on my report. The "Start Date" parameter defaults to today, and the "End Date" defaults to the "Start Date" + 1 Year.

This works fine in the Report Designer, e.g., when the Start Date is changed in preview mode, the End Date value is recalculated.

However, this behavior does not work in the Blazor Native Report Viewer.  When the page first renders, the two dates are shown correctly, but if the Start Date is changed, the End Date is not recalculated.

The Table of Contents(TOC) section is displayed at the bottom of the document map, despite appearing at the beginning of the rendered report itself. This can be confusing for the end-user.

We see a console error when navigating away from the Blazor Native report viewer page. The page that contains the breadcrumb and the viewer has query-supplied parameters.

Using the text-indent CSS setting results in part of the text on the first line being cut off:

 

I am using the obsolete `Telerik.Reporting.Chart` type for a chart in a report. When I attempt to preview the report, an error is thrown:

The type "Telerik.Reporting.Chart" contained in assembly "Telerik.Reporting, Version=19.2.25.1001, Culture=neutral, PublicKeyToken=a9d7983dfcc261be" cannot be loaded.
To help improve the application's security, the reporting engine prevents loading types that are not essentially needed or listed as trusted by the user. If you consider particular types or assemblies as trusted include them in the corresponding TypeReferences or AssemblyReferences element of the 'Telerik.Reporting' configuration section in the application's configuration file.

In MSSQL, you may use syntax like 'StoredProcedureName;1' to indicate stored procedure versioning, but it is not yet supported by Telerik Reporting.

I use such syntax and need to remove the version to make this work in Telerik Reporting.

It would be great if you also added support for versioning in MSSQL stored procedures.

I have enabled accessibility in my report viewer. The majority of the items do not cause any issues when using a11y scan tools like "Accessible Web Helper". However, shapes and empty text boxes are rendered without a "role" attribute, but with "aria-label", which causes conflicts with the a11y tool I am using. It states "aria-label attribute cannot be used on a div with no valid role attribute".

If you add transparency to a Graph line, for example, the Y-axis, with an alpha value: '150, 255, 255, 192', it is respected in the Standalone Report Designer, where the rendering format is Image.

In the Web Report Designer and in the HTML5 Report Viewer preview, the alpha value is ignored, and the color is rendered as '255, 255, 192', which removes the transparency.

Hi Team
We are using the Telerik Reporting component and are very happy
We really wanted to use the Table of Contents component in our reports
The Table of Contents works great but unfortunately does not support right-to-left in Hebrew
I guess for you this is a small fix and for us it will be a big relief
We ask for your help and improve the component for us so that the wonderful Table of Contents supports right-to-left
Thank you
Tamar

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.

Hi,

Currently, if Thread.CurrentThread.CurrentCulture set to tr-TR (can be also reproduced with az-AZ and maybe some other cultures) some tags are ignored in HtmlTextBox, but they work if typed in UpperCase. This can be reproduced with any supported tag which contains letter "i" like "div" or "li".

For example, we have two ol list but one with LI and the other one with li tags:

<ol>
  <LI>first</LI>
  <LI>second</LI>
</ol>

<ol>
  <li>first</li>
  <li>second</li>
</ol>

This is how it is rendered in PDF:

When the current thread culture is set to Turkish (tr-TR), the lowercase and uppercase conversion rules differ from English — especially for the letter "i".

• In Turkish:

  • "i".ToUpper() → İ (with a dot)

  • "I".ToLower() → ı (dotless i)

Our assumption that the Telerik HtmlTextBox internally parses and maps HTML tags by converting them to uppercase. When the Turkish culture is active, this conversion causes tag names to break, which is not a valid tag, so ordered lists fail to render.

Best regards,
Denis

ADA Accessibility is a priority for our customers, so we are aiming to ensure logical tabbing order for keyboard users.

I've noticed that the RowHeadersPrintOnEveryPage attribute, while very useful for creating more readable PDF exports, seems to result in some strange screen reader behavior when set to True.

The first problem is with the strange tabbing order in the live environment. The second column header is the first to receive focus, followed by the remaining column headers, then the data fields under the first column receive focus in a vertical list, until finally the first column header receives focus. Without the default RowHeadersPrintOnEveryPage setting (False), the first column header is the first to receive focus, which is expected. 

In addition to the wrong tabbing order, the RowHeaderPrintOnEveryPage causes the screen reader to announce the incorrect column associated with a particular cell. I use the Windows Narrator. Other screen readers may result in slightly different behavior.