In print preview, if you have "FIT_PAGE_WIDTH" as a default scale mode, once you click the "toggle full page/full page width" button, it's never possible to get it to return the original fit-page-width size (it seems to cycle between 3 different zoom modes, but none of them fill the entire control width).

It looks like the report viewer correctly sets the scale mode during initialization. However, when toggling the mode later, it sets it incorrectly.

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

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

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"  />

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

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.  

When a system tells users they should look into the report parameters as the reason the report isn't displaying.  It's reasonable for your users to believe you aren't misleading them. 

The report viewer error message misleads users.  In reality the parameters are correctly configured and it the repot URL could be wrong.  Or a variety of other issues are at play; for instance, a problem with you connection string will also return the "Unable to get report parameters" error message.  I'd like to see this error message at minimum changed to "report can't display."   It's better to throw out a generic message vs having users spend hours or days troubleshooting the report parameters.  Better yet a proper catch/validation system put into place please.  

I have a simple report with two TextBoxes in the detail section. In one of them, the content wraps as it doesn't fit, and in the other, it doesn't.

When I export to Excel (XLSX), under each detail section, there is an empty row.

When I left only the TextBox with the wrapping content, there were no empty rows in the Excel file.

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.