When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.

Additionally, images whose AccessibleDescription I have set are not read at all by those tools.

I have noticed that the performance of exporting reports has gotten worse in recent releases. After investigating, I found out that this is likely caused by the sheer size of the code in my projects.

To prove this, I created a simple application that renders a report to PDF programmatically. Then, I created 10 000+ dummy classes in the same project, and tried rendering the report again. The performance was noticeably impacted by this change.

If cells grow or shrink, if there are hidden cells, any time a report section grows vertically, the next section/table is not respecting the growing of the previous item and text prints in the wrong spot or the table overlaps the previous table.

A potential workaround is to manually convert the troublesome tables to lists where possible.

I have a report where I have placed a bunch of textbox items at the bottom of the page header that I use as headers for my data that I display in the detail section.

When I run the report in a Docker Linux container, where the Skia graphics engine is used, the items at the bottom edge disappear when rendering the report in the web report viewer(HTML5 Interactive) rendering.

The issue does not occur when I render the report with the "PRINT_PREVIEW" viewMode setting or when I use GDI+..

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

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.

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:

• The current page number
• The position of a specific control on the page
• Other Internal report variables

Benefits

• Enables precise control over report layout for complex, data-driven scenarios
• Improves usability for industries requiring strict formatting standards (e.g., financial, healthcare, compliance reporting)
• Aligns functionality with competitive reporting tools like Crystal Reports, enhancing product competitiveness
• Reduces manual workarounds and simplifies report design for advanced pagination needs

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 successfully installed the ODBC and OLEDB providers for Visual FoxPro 9 and they appear in the Windows 32-bit ODBC Data Sources under System DSN.

The drivers are discovered when I use Standalone Report Designer x86 from 17.2.23.1114 and older ones built against .NET Framework 4.0.

The same drivers are not found on the same machine when I use Standalone Report Designer x86 from 18.3.24.1218 built against .NET Framework 4.6.2.

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:

I load multiple variants of the Segoe UI font as private fonts in my application:

			<!-- Segoe UI -->
			<add fontFamily="Segoe UI" path="Fonts\SegoeUI\segoeui.ttf" fontStyle="Regular" />
			<add fontFamily="Segoe UI" path="Fonts\SegoeUI\seguisb.ttf" fontStyle="Semibold" />

This leads to issues, as there is no "Semibold" option in the System.Drawing.FontStyle enum.

The workaround that can be used to avoid this problem is to use unique font family names. For example

			<add fontFamily="Segoe UI" path="Fonts\SegoeUI\segoeui.ttf"  />
			<add fontFamily="Segoe UI Semibold" path="Fonts\SegoeUI\seguisb.ttf"  />

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 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).

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.

I use the kendovalidator before rendering the report to check the correct parameter of initial and final date.

However, the validation fails because additional inputs (for the "Send Email" functionality) are included in the HTML output of the viewer even though I have disabled it.

I believe that if the "Send Email" option is disabled the mail data panel should not be created.

All of my report parameters have their AutoRefresh setting set to False, and the parameters do not depend on each other, they are not cascading parameters. The parameters have available values.

If I change the value of one of the parameters, despite the above settings, all of the other parameters' data is re-retrieved(even if those parameters are not visible).

This causes issues because the "Preview" button is disabled until the parameters are refreshed, and makes the UX bad since if the connection is slow, the end-users will have to wait for the parameters area to refresh after changing any parameter value.