New development is being done with net core 3.1 and netstandard 2.1 and we can no longer create reports in the Report Designer using the ObjectDataSource.

Seems like it's time to update the standalone Report Designer for these new standards.

Problem description:
On ".net Framework" it is a supported scenario that assemblies with datasources and/or functions are loaded into the standalone ReportDesigner. This assemblies are used while designing and later also in the ReportViewer while executing the report. Feature described here https://docs.telerik.com/reporting/standalone-report-designer-extending-configuration

Now that .net 6 is release by MS the same feature is needed there. The problem is that the "standalone ReportDesigner" is targeting ."net framework" which means it can only load assemblies targeting ".net framework" or up to ".net standard 2.0". But that is not sufficient because on ".net standard 2.0" only EntityFrameworkCore3.1 is supported and all newer version (EF Core 6.0) are not.  See here https://docs.telerik.com/reporting/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core

So in summary:
It`s not possible to use EF Core 6.0 (and upwards) DataSources in the given "standalone ReportDesigner" because it is targeting .net framework. It`s critical to be able to use the newest EF Core versions as DataSource to not be blocked from upgrading a ".net framework" application to .net 6 where the described feature/scenario is used. I need to use the "standalone ReportDesigner" because it gets shipped with the application to edit the reports individually by the enduser. The "VS ReportDesinger" is going to get the upgrade but this would only be usable as a developer before shipping the application.

Feature request:
Upgrade the "standalone ReportDesigner" to target .net 6.

Steps to reproduce the problem:

Some corner case page size value force report processing to create an invalid page clipping during paging. 

Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.

It seems that the MultiSelect Combo Box Filtering does not work in the Report Viewer. o be smaller if the user starts typing

example of how it is removed

https://demos.telerik.com/reporting/product-line-sales

Trying to preview a report with a lot of data in the report viewer in an ASP.NET Core application results in the error:

"System.ArgumentException: The JSON value of length n is too large and not supported."

The Web Report Designer uses a subset of all available Kendo UI widgets. It will be useful to have a documentation article listing all of them, just as it's done for the HTML5 Report Viewer here: Kendo Widget Requirements.

This way the users will have better understanding which Kendo UI classes and components are used by Web Report Designer and will enable them making their own distribution packages when needed.

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

Please, add a .zip or .7zip with the following content from the Telerik Reporting folder:

• all runtime assemblies- everything from the Bin folder without the Design folder and VS<Version> (for example VS2019, VS2022, etc) folders
• Html5 folder
• License Agreements folder
• Silverlight folder
• Wpf folder

When generating a report with multiple tables provide the ability to send these tables to different workbook tabs when exporting to Excel

The parameters' area splitter's expand icon gets hidden when the area is shrunk.

When there is a textBox report item placed in a report page header/footer section with a text color styling applied to the textbox, the text color is not respected in the Excel export.

This happens only when the native excel page header/footer is used.

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?

When using the latest version of the Kendo Default Theme:

<link rel="stylesheet" href="https://unpkg.com/@@progress/kendo-theme-default@latest/dist/all.css" />

the export in the Blazor Report viewer does not work.

Meanwhile,  you can reference the older kendo CSS styles directly in the view with the ReportViewer. You may leave the new styles referenced on the layout page.  It works with:

<link rel="stylesheet" href="https://unpkg.com/@@progress/kendo-theme-default@4.26.0/dist/all.css" />

Currently we implemented the IDefinitionStorage to read and save files from azure storage

It would be nice if we could call the async methods

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,