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
Currently, there is an MCP server that allows for integrating and developing report viewers, report designers, and Reporting REST APIs through Copilot. Consider allowing end users without Telerik Reporting experience to also build reports using AI.
We have some issues with cut off texts on our PDF reports. It only happens rarely and only with some fonts.
TSE note: This is an investigation item for tracking purposes. The actual font is included in the private GitHub issue linked to this item.
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.
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.
Currently, page breaks in reports are static and cannot adapt to dynamic conditions during rendering. This limitation makes it challenging to format highly variable reports where layout requirements depend on runtime data or page positioning.
The requested feature would allow developers to define expressions or rules that determine whether a page break should occur, considering factors such as:
Similar, but more specific request already exists:
https://feedback.telerik.com/reporting/1356665-add-conditional-page-breaks-based-on-report-group-page-number-duplex-printing
See also my ticket: 1701322
I have a solution with two projects: one containing a report, and another for the objects.
The first one has a project reference to the second, and the objects are used within an ObjectDataSource component in the report from the first.
I open the solution, build the project with the objects, but the Data Explorer of the ObjectDataSource component in the first project with the report does not get automatically updated. I have to reconfigure the ObjectDataSource manually for the change to take effect.