I have scenario like this: Sam requests a product report from company A.  Marvin creates the report and send it back to Sam.  Sam imports it.  It would be best if Marvin (Author of the report) could specify all the meta data so that Sam doesn't have to enter these things.

In my case I need following metadata for the report:

• Keyword: some external tags...
• Description: a description so that the user can understand what this report will show and the purpose of the report.

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;
    }
}

We are using Telerik Report Viewer in our ASP.NET MVC application. I've read the documentation about localizing the report viewer (https://docs.telerik.com/reporting/html5-report-viewer-localization) and most of the texts are localized now, but there are some other that I can't change.

For example, in the search menu, result list, 'page xx' text.

Can you add this string resource in the resources file?

Prerequisites: .NET Core application that uses HTML5-based report viewer and REST service with Kestrel web server.

When the application is stopped from the command prompt with CTRL+C, it does not stop all the dotnet.exe child processes that are spawn by the application and hangs on "Application is shutting down..." indefinitely.

This behavior might be related with the issue https://github.com/aspnet/Hosting/issues/960 which states that CTRL+C is not forwarded to the child processes.
Perform a detailed examination to see if there is an option to close the processes internally when a shutdown procedure is initiated.

When a textbox had a value and after that the value was deleted, if you try to set a language for the report the following error message occurs: "textbox26.width cannot be parsed as a unit because it does not contain numeric values. 

Hello,

I have been working on some reports that require multiple tables on a single page. This limits the space columns have for data being bound to fit and results in text wrapping. I made a support ticket asking if there was a way to have dynamic column widths. I hoped to find a way to get table columns to change their widths depending on the data being bound to the table, while still maintaining the overall width of the table. My idea was to have it distribute the space (change the column width) to best display data and avoid text wrapping if possible. 

Attached to this request are some PDFs. One of them ("Current Report") shows that some data is either cut off or uses text wrapping. The other attached PDF shows the closest I could get to an acceptable layout, given our clients requirements and what our design team wants the reports to look like.

Thank you!

It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.

If you have a lot of graphs in your report then it is more convenient to change the color palette one place.

Asking to enable typing into the font combo box in standalone Telerik Report Designer.

The concept would be to click on the font drop down and just start to type the name of the font and have the list shift to that position for you.

When exporting a long report with ContinuousPaper = true in Word format, the output document has text cut.

Based on the limitation explained in the Pagination section in Design Considerations for Word Rendering article of our documentation, Word supports maximum page size of 22 inches wide and 22 inches high. If the page is higher than 22 inches, some data may not be displayed in Print Layout view. So, in Word, a long document couldn't be rendered.

At least, this property could be avoided when printed in Word format.