When Windows display scaling is set to 150%, the stand-alone report designer causes the resulting Excel Worksheet export to shrink from its expected layout.

Steps to reproduce:

1. Set display scaling to 150% in Windows Display Settings
2. Start the standalone Telerik Report Designer and open the Invoice example report
   
3. Preview the report for order SO51081 and export to "Excel Worksheet"
4. Open the report in Excel.
   Issue: Its formatting is not as expected, note the contact name is cut off and overall the output is squished together.
5. Close the Telerik Report Designer
6. Set display scaling to 100% in Windows Display Settings
7. Repeat steps 2 through 4 and note the improved rendering of the Excel Worksheet at standard display DPI.

I've attached my XLSX file results for 150% scaling and 100% scaling to show the problem.

I would not expect my display settings to alter the export of Excel Worksheet files in the Telerik Report Designer application.

150%:

100%:

Standalone Report Designer is not localized when the trdp file is opened. The localization only takes effect when the executable file is started first and then the report is opened. 

Reproducible in R2 2020 14.1.20.513

It would be good if the table headers can be frozen.  This can  be really useful in case of a big report which is displayed on a single page.

If during the report rendering stage, one or more of the required entities in the File storage were removed/deleted by third-party software, it will prevent the report from finishing the rendering and throws a NullRefereceException:

Print functionality doesn't work in React application.

Steps to reproduce:

1. You may use the sample project from How to use HTML5 Report Viewer in React Application article.

2. Run the project and click on Print.

The following error can be seen in the browser's console: Resource interpreted as Document but transferred with MIME type application/pdf: "https://demos.telerik.com/reporting/api/reports/clients/a7fdd020ec4/instances/3f53abd1614/documents/c3923e685e6d6ebefb3d11?response-content-disposition=inline".

When exporting to Excel Worksheet, the CheckBox item is rendered as Excel Picture. If the machine settings are higher than the default 96 DPI (100%), the checkbox image is generated with incorrect size and the produced Excel file is corrupted.

Steps to reproduce:

1. Create a Blazor application;

2. Add Teleri.Reporting NuGet package;

3. Add Telerik.WebReportDesigner.Services Nuget package -> some of the app dependencies are broken.

Solution:

Refer the .NET Standard DLLs from C:\Program Files (x86)\Progress\Telerik Reporting <Version>\Bin\netstandard2.0.

Please add support for Data Matrix barcodes.  As of Q3 2014 this is the only format we will still need to rely on another library to create an image that is placed in a picture box.  We would much rather be able to use the Barcode control for all our barcode requirements.

It would be very handy, if the value property of the PictureBox would resolve images from base64 strings besides the Image, Image byte[], relative or absolute URI.
It should be fairly simple to implement. I wrote my own user function for this. It would be beneficial to have this out of the box.

[Function(Category = "Image", Namespace = "ImageFunctions", Description = "Converts a base64 string to an image byte array")]
public static byte[] ConvertFromBase64(string imageString)
{
    if (imageString != null)
    {
        // Convert base 64 string to byte[]
        byte[] imageBytes = Convert.FromBase64String(imageString);
        return imageBytes;
    }
    else
    {
        return null;
    }
}

When the SqlDataSource wizard uses a connection to a non-MSSQL database, which is registered in a Report Server instance, previewing the results on the "Preview data source results" page will throw an exception.