Hi,

Does the Web Report Designer support zooming of the report area? Similar to the Standalone designer:

Best regards,

Magnus

Please add DropDownTree and/or TreeView as single- and multi-value parameter editors to accommodate Hierarchical data. It would be nice to have them out-of-the-box when available values come from a hierarchical/self-referencing table(s), but I would be happy if they could be integrated as Custom Parameter Editors. I was able to render and populate the dropdowntree with checkboxes, pass the correct selected values, but the 'Preview' button would never enable upon selection. Also, the dropdowntree's AutoClose(false) was not recognized. I know this can be achieved outside of the report viewer, but sometimes that method disrupts the layout and flow of the reporting view.

Issue #1: In WinUI3, for Telerik Report Viewer, when we have a link to URI to open in a new window, it is not working correctly.

Here is a setting in a demo report (Report Catalog): 

When clicking to link in control on runtime, we are getting the following error:

This looks like a bug.

Issue #2: Our scenario is the following: We will have some custom links in a report like, "MyApp:Customer/TEST". When we click on that, we need to send that link to our WinUI app, which will let's say navigate to a Customer page after it is clicked in a report. Due to Issue #1, we were not able to test it. Even when Issue #1 is resolved, what is a good way for us to handle the current scenario? I don't want to refresh the report when some link is clicked.

Issue #3. We might have the HTML Text box in a report. When it has a link, it is not clickable. This is another item that looks like a bug.

Can you please help to resolve these 3 issues?

Thanks,

Hi Team,

I would like to request an HTML5 ASP.NET Core Report Viewer similar to the MVC version with wrappers.  It would be great to be able to utilize Razor Syntax for developing instead of pure jQuery.

Thank you!

The overlap warnings may clutter up the page.

It will be a good option to be able to switch them off. The reason is that most of the time I want to ignore them because they actually do not cause problems. If I want to turn it on to check I would be able to.

React Report Viewer throws error ts(7016) on importing it in a TypeScript project:

Could not find a declaration file for module '@progress/telerik-react-report-viewer/dist/cjs/main'. 'C:/Users/dnikolov/Desktop/ReactTypesScript/my-app/node_modules/@progress/telerik-react-report-viewer/dist/cjs/main.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/progress__telerik-react-report-viewer` if it exists or add a new declaration (.d.ts) file containing `declare module '@progress/telerik-react-report-viewer/dist/cjs/main';`

When the font that is used to generate the report is not installed on the client machine, some of the text may be cropped

t would be very useful to be able to embed fonts in DOCX and the other OpenXMLs, as in PDF.

Clicking the cancel button on the HTML5 report viewer show "Report processing was canceled" in the UI but the report is still being generated and rendered on the server.

In this old thread it is stated that it isn't possible to cancel the report generation on the server. Is that still the case?

Please add the Web Report Designer Item Template for VB.NET projects too

Currently, the WinUI ReportViewer has a hard dependency on Windows due to the fact that the internals rely on the Win32 print dialog.

This means I cannot define the ReportViewer in a WinUI class library to be shared with multiple front-end WinUI projects. If you attempt to do this, there's an internal crash because the project cannot resolve  System.Windows.Forms.

This feature request is ask if you can replace the Win32 print dialog with the WinRT printing API. 

Research Note:  Here's a GitHub thread where Microsoft is discussing the topic Question: Printing in WinUI 3 Desktop · Issue #4419 · microsoft/microsoft-ui-xaml (github.com). Here's their current recommendation:

var hWnd = WinRT.Interop.WindowNative.GetWindowHandle(App.StartupWindow);
var printMan = PrintManagerInterop.GetForWindow(hWnd);

await PrintManagerInterop.ShowPrintUIForWindowAsync(hWnd)