When my application is hosted on Windows, Arabic date values appear reversed in the day part during PDF export with the Skia graphics engine. For example, 2025/01/01 is displayed as /01/10 when Arabic digits are used.
With the GDI graphics engine, the Date values are rendered as expected.
My use case is a multi-select parameter that is based on a dataset; and the dataset is filtered by 2 other parameters.
The dependent parameter editor is shown as a SpinButton rather than a multi-select editor in the Blazor Native Report Viewer:
Using the text-indent CSS setting results in part of the text on the first line being cut off:
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.
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 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.
---
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.
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.
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.