Hi Team,

Currently, the Angular Report View doesn't appear to support the Ivy rendering. As of Angular 16 (released 4 days ago), the legacy rendering mode is fully removed. Which means the ReportViewer will no longer work in ng16 or later.

So this feature request is to move the ReportViewer to support Ivy (which will support Angular v9 to v16 and later).

Thank you,

Maks

There is a common error message received often after upgrading Telerik Reporting:

Unable to get report parameters. An error has occurred. Cannot read a document with the specified schema: http://schemas.telerik.com/reporting/2023/1.1. You might be using an older version of the product.

Obviously, I have a mismatch between the new report that I created and the deployed Reporting application. To create the report that is generating this error, I copied from an existing (and working) report.  Only changed the Stored Proc being called and a few field names.  Everything else is the same.

Except -- (OBVIOUSLY) -- when I saved the report -- the Designer changed the schema version. 

You need a way in the DESIGNER to display the schema version of the report. If these reports are TRDP then I don't see an obvious way of viewing the schema version of the report. I opened both reports in the designer and tried to find a way to view the schema versions of a working versus non-working report.  So that, I could determine which version of the designer that I need to drop back to (in order to create my copy of an existing report).

In your error message, you could easily provide additional detail but do not. You just say "product". Obviously, you know this but you don't report it to user.  For example, you could say -- "This report has schema version xx.xxx.xx but the Reporting Engine can only run reports of schema version yy.yyy.yy and below" or something to that affect.  Good error messages would go a long way to avoiding this frustration.

Some SVG files are not rendered as expected when the PDF Rendering is used.

SVG opened in the browser:

SVG in rendered PDF file:

I just migrated from building with react-scripts to Vite, as it seems react-scripts is deprecated. After the change, the react report viewer is not functioning correctly. Browser console shows:

Instantiation of Kendo TreeView as Document Map threw an exception TypeError: $kendoHtmlEncode is not a function

Uncaught (in promise) TypeError: $kendoHtmlEncode is not a function

Currently, the parameters' editors of the WRD's internal viewer cannot be changed. A report parameter with available values is always rendered with the ListView widget.

I would like to be able to use the viewer's built-in ComboBox widget as shown in the HTML5 Report Viewer Options Overview - Telerik Reporting article, and to also be able to use a custom one.

The CSV renderer ignores the visible state of elements in a report definition (sections, headers, footers, text boxes etc.) with the Visible property to false - either explicity or by binding.

This results in much redundant content in the CSV file, that is often not even the actual output/result data - which should be the primary focus of a format like CSV.

Being able to control the output brings much flexibility to the CSV feature. Though Reporting primarily has a focus on a more rich, visual display of data, having access to the same "raw" result set that a report would evaluate can be very useful, without having to try replicate through other means.

Binding the Visible property of elements to: = RenderingFormat.Name <> "CSV" would allow the choice of including what makes sense in the ouput, even allowing a different "view" of the data, which could contain just detail row fields or additionally, summary fields from group and report headers & footers.

Previously, the Processing.PictureBox property Image required a System.Drawing.Image.

Starting with R3 2023 it requires Telerik.Drawing.IImage, and throws the exception:

Cannot implicitly convert type 'System.Drawing.Image' to 'Telerik.Drawing.IImage'. An explicit conversion exists (are you missing a cast?)

On .Net 6, exporting html5 produces multiple html files including a single report having multiple pages are split into multiples. Could we please have the feature similar to MHTML export in the previous .net versions supported. This is a breaking change when upgrading to .Net 6. 

Thanks!

When my application runs in full trust permissions set, the following error is thrown if I have used the Telerik.Reporting.OpenXmlRendering NuGet package and try exporting to any of the OpenXML formats :

ERROR: Attempt by security transparent method 'Telerik.Reporting.OpenXmlRendering.Spreadsheet.Workbook..ctor()' to access security critical method 'DocumentFormat.OpenXml.Packaging.SpreadsheetDocument.Create(System.IO.Stream, DocumentFormat.OpenXml.SpreadsheetDocumentType)' failed.

When I open a tab that includes the Angular report viewer and close it immediately after, before the viewer can be properly initialized, the following error will be thrown:

core.js:7744  ERROR Error: Uncaught (in promise): TypeError: perspectiveManager.dispose is not a function
TypeError: perspectiveManager.dispose is not a function
    at Object.dispose (telerikReportViewer.js:8447:30)
    at TelerikReportViewerComponent.ngOnDestroy (telerik-report-viewer.component.js:61:27)
    at executeOnDestroys (core.js:6118:1)
    at cleanUpView (core.js:6021:1)
    at destroyViewTree (core.js:5847:1)
    at destroyLView (core.js:5999:1)
    at RootViewRef.destroy (core.js:22750:1)
    at ComponentRef$1.destroy (core.js:25284:1)
    at RouterOutlet.deactivate (router.js:5577:1)
    at ActivateRoutes.deactivateRouteAndOutlet (router.js:2101:1)
    at resolvePromise (zone.js:1211:1)
    at resolvePromise (zone.js:1165:1)
    at zone.js:1278:1
    at _ZoneDelegate.invokeTask (zone.js:406:1)
    at Object.onInvokeTask (core.js:28767:1)
    at _ZoneDelegate.invokeTask (zone.js:405:1)
    at Zone.runTask (zone.js:178:1)
    at drainMicroTaskQueue (zone.js:585:1)
    at ZoneTask.invokeTask [as invoke] (zone.js:491:1)
    at invokeTask (zone.js:1661:1)

If I use an HTML5-based Report Viewer with the default CONTINUOUS_SCROLL page mode and I start scrolling to the next page, the Get Document Page request is made multiple times for the same page.

If I move to the next page via the toolbar buttons or if I use the SINGLE_PAGE page mode, then problem is not reproduced.

I have a table with grouping and GroupPageBreak set to After for the group.

In the detail cell of the table, I have a Panel with a Crosstab in it. The Crosstab has row groups, however, their properties are the default, hence, they don't force any Page Breaks.

When the report is previewed or exported to PDF, each table group is on its own page as expected.

I have set SplitWorksheetOnPageBreak to True for Excel rendering, so that each soft page, i.e. Crosstab in the table group is in a new worksheet.

This works fine, except that the first table group is split into two worksheets.

I have a table with a detailed group with PageBreak set to 'After' and a crosstab inside the table with a row group that also has PageBreak set to 'After'. The pagination is respected in the preview of the designer, however, when exported to XLSX, there is only one worksheet generated.

If I remove only the PageBreak of the detailed table group, there is no pagination and the generated worksheet is only one.

If I remove only the PageBreak of the crosstab row group, there is pagination and the generated worksheet is correct in number. However, the content is not split as expected among the sheets.

If I make the detail table group static and remove its PageBreak, the pagination and the worksheets of the Excel document are as expected.

I am trying to implement the ISharedDataSourceStorage interface and the SaveAsync method receives a parameter of type SaveResourceModel from which I cannot access the description that the user might have written in the UI.

The support team told me that the FileSharedDataSourceStorage class internally uses a SharedDataSourceDescriptionHelper class for accessing the description. 

Please make the helper class public so that we may also use it when implementing the ISharedDataSourceStorage interface.

I think navigating over pages by click is boring/complicated, scroll over pages seens to be the standard in the majority of applications.

I know that the HTML5 ReportViewer has the pageMode() property to solve this...

There's a way of implementing the PageModeProperty into the WPF ReportViewer?

Some special characters, such as "🍁", break reports that are rendered with the Skia graphics engine in a Linux environment.

When the Gdi graphics engine is used on Linux, the reports are generated successfully. However, the Gdi graphics engine cannot be used on Linux with projects that target .NET 7 and later.

I am using the Blazor Web Report Designer widget which when initialized, loads its theme based on the @progress/kendo-theme-default - npm (npmjs.com) theme and overrides the styles in my Blazor application. There is no way to disable the loading of the designer's theme and the application looks inconsistent as a result.