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.

The editor for parameters can be set for each type of parameter, but not individually for each parameter.

This means if there are two parameters that both have availableValues and have multiselect set to false, different editors can be set for each of these two parameters.

Exclude(hide/show) a report from Report Book based on ReportBook Parameter

A PictureBox item containing an SVG file does not size as expected when Sizing property-options are set to either "Center", "Normal" or "Stretch", and then exported to PDF.

Transparency is not respected when a report is exported to PDF format. 

Shapes inside of an SVG file can have transparency applied to it through styling or attribute, but neither of these options work when exported to PDF. In the Report Viewer the SVG renders correctly and shapes can be transparent, but when export and viewed as PDF, shapes become opague.

In my scenario, I save the ReportSource instances in a dictionary in the custom ReportSource Resolver:
However, I have no chance to delete the memory because there is no event or flag to see when it is not needed anymore.

The path for window.kendo in initExpDeps.js is incorrect. This does not always lead to error. When there's an error it can be the following:

Module not found: Error: Can't resolve '.\telerikReportViewer.kendo.min'" in "ERROR in ./node_modules/@progress/telerik-angular-report-viewer/dist/dependencies/initExtDeps.js

When WPF Report Viewer inside other control (e.g. TabControl) all events (PrintBegin, PrintEnd, ExportBegin, ExportEnd etc.) fires twice, because Loaded event fires twice and you call AttachModelEventHandlers method also twice.

In the Report properties of the Web Report Designer when you open Layout -> PageSettings, there is no input or other control where you may enter or select any values or measure units for the Margins.

Currently when the report starts loading, the viewer clears all of its areas and shows a series of notification messages that specifies the current stage of the report loading workflow. The report viewer areas are populated again when the first page of the report is displayed in the report viewer. 
In a scenario where the report needs a lot of time to load this behavior is not optimal. In such case the report viewer areas should not be cleared until the first page of the new report is prepared to be displayed in the viewer. The developers should be able to configure the loading behavior and notification message appearance through the report viewer options. The viewer's API should also provide event handlers for these events, so the developers can have more control over the page displaying process.

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

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

To sum it up:

Please add .NET 5 js/css isolation to Blazor ReportViewer which will allow:

• usage of more report viewers with different report engine services during the application lifetime (current design requires to load js/css globally from single report engine service and the js cannot be unloaded because it is not isolated in a module)
• simpler usage of the viewer which should just require to set ServiceUrl and the js/css would be managed by the component itself

Currently, the MsSqlServerStorage CommandTimeout is with the default value that is 30 s. In some scenarios, like when the Search functionality is enabled and the report is very big, the generated ClientSearchItemsResource may be too big, and when attempting to save it in the storage the latter may throw the exception 'System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.'

The error may be avoided if the CommandTimeout can be increased.

The SearchDialog is placed based upon a parent window of type "Window". However, when I use other types like "RadRibbonWindow" as my main window the placement does not work correct. As a result the SearchDialog is shown in the upper right corner of the desktop. This is the code (in SearchDialogController.cs):

        Window GetParentWindow()
        {
            return (this.model.PageScrollViewer == null)
                ? null
                : this.model.PageScrollViewer.FirstParentOfType<Window>();
        }

At least this method should also take RadRibbonWindow in account (this is certainly not used that rarely since we all use Telerik components!) or for a more generic solution look for types that are derived from Window.

Please add a property "ToolbarVisible" to WPF ReportViewer. Most of the cases the buttons are not useful or should be replaced by some custom toolbar. 

White space appears between different rows. Depending on the zoom level it could happen on one or more rows.

I will attach a report example to this message.

Steps to reproduce:

1.Download and run the project

2. If the scaleMode is FitPage, the report doesn't appear

3. If the scaleMode is FitPageWidth, the UI seems to be broken

You can check the attached video for further reference.

 

Steps to reproduce:

1. Download and run the attached project in IE or Firefox

2. Write in the field for example "haha" and click the button.

3.Scroll down and you will notice that the headers are not frozen.

Hello Team,

 

I will be great if the Telerik Reporting REST Service Core could support System.Text.Json serialization.

 

Best Regards,

If you open https://demos.telerik.com/reporting/designer?_ga=2.145120566.369274565.1605642252-790264781.1600201366 the problem can be seen.

Select one of the TextBoxes such as TextBox1

Select the Layout > Size Properties of the TextBox

Try to change the Width to 3.5 in.

Notice the Width goes to 35 instead of 3.5

This is the same case for Location > Left & Top and Size > Height