I use an approved government font for the reports. I have specified it in the `privateFonts` option of the report engine configuration. However, on Linux, it is not picked up during rendering. In FontForge, the font shows the following warning:

On Windows, it causes no issues.

When adding an embedded image to a coded report in the Standalone Designer .NET, the original RESX file is not modified.

Only the original DESIGNER.CS file is modified. This leads to the new PictureBox being present but empty after deleting the dedicated folder named after the report (beside the designer EXE).

I have an image set to the checkbox through the CheckedImage property. When I export the report to Excel using the Skia graphics engine, the image is not present at all, or cut off.

The same issue is not present in the GDI engine or with the PictureBox item.

My table may contain text consisting only of repeating '1', i.e., "11111111111111111111111111111111". When this content cannot fit inside a single line, the Table generates a second row; however, part of the content spills out to the next Table column.

With other repeating characters like 'I', 'l', '2', and 't', the issue didn't reproduce. When the line contained other characters, the problem didn't occur as well.

I want to set the Table ColumnWidth to a particular value in the Properties of the Web Report Designer. There is no property ColumnWidth as in the Desktop designers, and I tried to set the Size.Width, which is available.

When I increased the Width from the Properties, in design time, there is no change in the column width, only dashed borders indicating the new size when selecting the corresponding TextBoxes. In runtime, though, the new size is respected.

The inconsistency repeats even when I open the saved report in another browser or through another application, hence this is not a caching issue.

Hello Team Support,

I work with the ReportViewer in WPF. I modified the description of some format in my App.config.

When I export my report, if the description is too long, it does not fit the message window anymore.

Here is a screenshot of my issue:

Thank you in advance.

Best regards,

Jonas

My application uses RadDocking. When the WPF Report Viewer is hosted in RadDocking, some Graph labels appear cut.

The problem is related to the property UseLayoutRounding="True" in the RadDocking.

The workaround is to use the following setting:

RadPane pane = new RadDocumentPane();
pane.UseLayoutRounding = false;
pane.Header = "Report";
pane.Content = reportViewer;
DocumentPaneGroup.AddItem(pane, Telerik.Windows.Controls.Docking.DockPosition.Center);

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.

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.