In the WebReportDesigner, when resizing a table cell on the designer-Element (NOT through the properties area), the Units of width and height are always reset to pixel.

The selected unit should not change when resizing the table cell/column/row.

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.

My need is to format numbers according to a custom culture with custom decimal, group symbols and number of decimal digits. For this I've created a custom CultureInfo object and set it up on Report.Culture property in a IReportSourceResolver implementation - I am using ASP.NET  from .net 5 example. For some reason, most of the NumberFormatInfo properties are ignored and a default, specific to the underlying culture code, is used. 

I need to programmatically change the NumberFormatInfo, because the service that is using Telerik Reporting is working in a multi tenant / multi culture environment and it must use the same report template but with different cultures for different requests.

Current result:

123 456 789
123 456 789,012
123 456 789 €
123 456 789,01 € 

Desired result, as per NumberFormatInfo settings (seen also in console):

123#456#789

123#456#789*01235

123##456##789 E

123##456##789**012346 E

Documentation reference:

https://docs.telerik.com/reporting/designing-reports-report-globalization

"A report is globalized with the help of a System.Globalization.CultureInfo object. You can specify a Culture for the entire Telerik.Reporting.Report by setting its Report.Culture property. This will force all Telerik.Reporting.TextBox items to respect the assigned Culture." 

But this does not appear to fully work. NumberFormatInfo of the Report.Culture property is not considered.

I've attached a project that reproduces this issues.

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.

1. The design-time preview of the HtmlTextBox throws the "Name cannot begin with the '>' character..." error when the not equal (<>) operator is used in the value expression as it incorrectly tries to parse the operator as HTML markup. The standalone designer does not have a design-time preview for the HtmlTextBox and the issue is not present there.

This does not affect the actual preview of the report and can be worked around by negating the equal (=) operator using the Not operator instead.

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

3. 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. Again, 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 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.

Reproducible in version: 18.2.24.924 +
Not reproducible in version: 18.2.24.806

Description
In releases before 18.2.24.924 it was enough to open dll with types from SRD in order to be able to import the type reports. Currently, this is possible only if you copy the dll next to SRD exe file and add entry in Assembly References for the dll.

Steps To Reproduce

Build the project CSharp.ReportLibrary.csproj in C:\Program Files (x86)\Progress\Telerik Reporting 2024 Q4\Examples\CSharp.NET Framework\ReportLibrary
Start SRD FF and from Open menu select the CSharp.ReportLibrary.dll dll in C:\Program Files (x86)\Progress\Telerik Reporting 2024 Q4\Examples\CSharp.NET Framework\ReportLibrary\bin\Debug
Expected behavior
Something like "Please add first Assembly reference to the dll... from ...". Or even better. Do you allow the assembly ... to be loaded? And we can add the assembly reference instead of the customer.

Actual behavior
TypeReference error.

When I drag a data field from a DataSource component to the Report details section in the Standalone Report Designer, the Report > DataSource property is set automatically to the corresponding DataSource component.

In the Web Report Designer, when I drag a data field, the Report > DataSource property remains empty, and the Preview shows an empty report. It would be very helpful the same functionality to be introduced also in the Web Designer.

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.  

I am using Kendo UI R1 2023 SP2 (version 2023.1.425) themes. Telerik Reporting scripts and stylesheets have not been updated to reflect the latest changes of Kendo UI.

1st photo shows using bootstrap themes, 2nd photo shows using other themes. 

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.