Please, add an option in the Standalone designer which will allow the user to select if the designer will be opened in full-screen mode or not.

In the ReportProcessor, it would be interesting to be able to capture the log.
Since it is shown on the Console. And if possible to have other statuses such as generated the query, loading resources etc ...

Processing report
Rendering report

You can also calculate an estimated time to process / render.

Tranks.

The JsonDataSource component escapes characters like quotation marks in the Web Report Designer, which makes the JSON invalid.

Hello, 

 

It would be nice if Telerik Reporting supported an organizational chart type like in ASP.NET AJAX. See the following image for a reference. 

 

Hello,

I am working on Blazor reporting project and I have described the situation already in this post:

https://www.telerik.com/forums/report-viewer-and-web-designer-in-blazor#zGr6FO2mDEmkfLWIP_T_9A

Please add Blazor ReportDesigner wrapping Your HTML designer and use .NET 5 js/css isolation to manage js/css loading by the component itself and not globally.

 

Thank You

Marek Ištvánek

The design-time web service data source parameter values are not displayed in the Web Report Designer while correctly read by the Standalone designer.

The run-time web service data source parameter values are displayed as [object] rather than expressions.

Check this screenshot for clarity.

I have a sub-report with cross-section items that works well.  Then when I use the sub-report in the main report the cross-section vertical lines disappear.

The default value of the report property SkipBlankPages is True and when there is an error in the report, for example, due to a problem with the connection to the database, the error message may be hidden as the report is not rendered at all.

The report should be rendered in order to display the error message also when SkipBlankPages is True.

Currently, if the SkipBlankPages property is set to True and there is not any significant content in the report, the following message will be displayed in the designer and the viewer: The current data set presented in the report did not produce any significant content, so no pages were generated. If you need to see the whole report content, including blank pages, please contact the report author.

I use <strong> to make part of the text in an HtmlTextBox bold. When my report is rendered in PDF under Linux, the bold text overlaps the normal text. The issue persists even when I put the text with different styles in separate <span> elements.

The customer should be able to disable printing, text and graphic selection and extraction, page rotations and others.

There seems to be no way to create a Style Rule with Style Selector in the Web Designer. The only option available is Type.

Due to breaking changes related to the Kendo state classes - https://docs.telerik.com/aspnet-core/styles-and-layout/components-rendering-overview#state-classes, report parameters loaded in the HTML5 Report Viewers that use the ListView widget, are not selected properly, thus the report is not updated with a new report source and the data does not change.

 

I would like to be able to decide whether a Web Report Designer user can edit or not a SharedDataSource component dynamically. Not all users should have access to this functionality. 

The background image of a report item is not sized correctly when exporting in PowerPoint format (PPTX) and have the UseMetafile flag set to false.
If the flag UseMetafile is set to true, the image is rendered as expected.

When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.

The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.  

Standalone Report Designer crashes on start when opening TRDP reports from Visual Studio. See the attachedimages below:

The stack trace came about after trying to open multiple files through VS and popped up after about report number 3 or 4. Lastly, for us "sometimes" the reports open, sometimes they don't. If it does open the report going through VS, then the Standalone Report Designer will randomly shut down/crash with no errors (after 5 to 30 minutes of active use. We haven't found a pattern for what makes the Designer crash.

So far, the Designer doesn't crash if started from the Windows Explorer.

Will it be possible to configure the stand-alone report designer to use the Skiasharp rendering engine when generating export files from the preview? This would help us verify that what we see at design-time is similar to what is being generated at run-time. Currently we have to copy report files into a Linux docker container to perform this type of testing.

Holding the Shift key should allow the selection of multiple items at once.

The current implementation of the WebAPI ReportController requires that is run as a Singleton. When running on Azure with multiple instances, it doenst work well. For deployments with large amounts of HTML reportviewer clients, one report server is not enough, it needs to scale. I suggest putting shared reportcontroller state (resources) in a configurable external out of process multiple concurrent access safe data structure. Solutions could range from database to shared in memory nosql, for instance Redis or Azure cache.