The Web Report Designer lets the user change the size of a TextBox inside a Table cell from its Properties. The change is also visualized in design time. For example, if the TextBox is enlarged, it sticks outside the table.

The above change is not respected in the preview of the web designer.

I would expect such a resize to be impossible, as in the Standalone Designer; or the entire table column/row to change its size accordingly.

The report items that have explicitly set background in the report definition are not highlighted by the Search functionality of the viewer when their content matches the search.

Reproducible with Blazor Native Report Viewer.

Partially reproducible with HTML5 Viewer - the highlighted (when selecting the item in the Search list) class is applied but the shaded is not.

The workaround is to use the following styles on the page with the viewer:

<style>
    .trv-report-viewer-wrapper .trv-search-dialog-highlighted-result {
        background-color: rgba(0, 35, 102, 0.3);
        color: #fff;
        background-image: none;
    }

    .trv-report-viewer-wrapper .trv-search-dialog-shaded-result {
        background-color: rgba(255, 140, 0, 0.3);
    }
</style>

If the  Telerik.ReportViewer.WinForms.ReportViewer.ReportSource property of the WinForms Report Viewer is null, besides displaying a message that no report has been loaded, the parameters area is also visible.

The parameters area shouldn't be visible when no report is selected, only the message should be displayed in the viewer's viewport.

The design-time preview of an HtmlTextBox located in a data item throws a null reference exception when it has a conditional formatting rule that changes the appearance of the HtmlTextBox based on the RowNumber data function. This function cannot be executed successfully during design time as the data is not available yet.

Since this issue is also related to the preview during design time, it does not affect the actual report preview either.

 The design-time preview of the PictureBox throws a null reference exception when it has a binding that changes its value based on one of the fields from the data source. The preview incorrectly tries to respect this binding which will not work in design time as the data is not fetched at this point. Instead, the design-time preview should use the default value from the Value property of the PictureBox, which is what the standalone designer does.

This does not affect the actual report preview.

Watermark Images with higher than the report rendering DPI are displayed clipped in PPTX rendering.

In PDF, preview of the designers and DOCX the same watermark is shown as expected.

If the DPI of the image is 96 as the default Windows machine DPI used for rendering, the Watermark is displayed correctly also in PPTX.

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.

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.  

DPI Awareness Settings are not applied when printing from the ReportProcessor in .NET where the configuration is provided in the constructor.

However, if I manually invoke the SetProcessDpiAwareness function before triggering the printing, the DPI is successfully updated.

Just like the HTML5 Report Viewer, it will be easier to embed the Web Report Designer in an application if it wasn't necessary to manually add the kendo script to the page.

I have a use case which requires me to record data whenever a report is printed. In pursuit of this, I am trying to replace the build in Print() tool and replace it with my own.

I have read this documentation which shows how to remove and reorder the buttons well enough, but it does not support adding a new tool all-together. Javascript event listeners will not work for me because ultimately what I want to do is accomplish a database write, which would be insecure through javascript.

 I have been able to establish a workaround by following this documentation and creating a button *outside* of the ReportViewer, however, I would still like to find a way to put the button inside of the ReportViewer toolbar if possible. 

Group properties are not visible in the item tree of the Telerik Report Designer for .NET.

I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.

It would be very useful if we could copy/paste Report Parameters between reports.

Currently, the Native Angular Report Viewer does not support NodeJS 22. It is restricted to v16-21 of NodeJS and I would have to downgrade to use it.

Old shortcuts(CTRL+INSERT: Copy, SHIFT+INSERT: Paste and SHIFT+DELETE: Cut) of cut/copy/paste don't work in Standalone Report Designer for elements.