Please, run the attached report. We would expect that the exec function will return the sum of debits from the table2, however, the scope is returned as invalid.

When a report is rendered by the REST Service, and that report has an element with applied 'Navigate To Report'-action, the full path of that file is being used as a reference, instead of a relative path or just the report-name.

Then the HTML5 ReportViewer is set to pageMode SINGLE_PAGE and an update triggeres the Viewer to retrieve the document, the new document is never displayed. 

Status messages appear as usual, "Loading report", "0 pages loaded so far" and "Done. Total 1 pages loaded." but the gray overlay of the Viewer is never removed and the report is not updated. Parameters and toolbar-menu can still be interacted with and trigger new updates, but will not cause the viewer to show the report correctly. Refresh required

There are two issues I observed with the Web Designer:

1.If you edit any Report Parameter Value from Designer it will convert to [object Object]

2. And clicking the ellipses (...) to edit the value, opens and closes the modal dialog sometimes.

Please see the attached report for a reproduction of this behavior.

As you can see, the crosstab has only one row group in the group explorer which has its PageBreak property set to None. However, in the report explorer, you can see a greyed out row group I deleted with PageBreak=After which results in page breaks being inserted even though the group was supposedly deleted. In order to reproduce this, it appears that you have to first delete the column only and then delete the group, and you are left with a grey "ghost group" in the report explorer. If I delete both at once this does not seem to happen. I'm on version 15.0.21.120

The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.

Exporting a report as PDF produces a corrupted file as soon as it reaches 2GB or more in file size. Available client memory should have been enough and was not at its limit. We have built the application as x64.

We use large-sized image files in the reports.

If any schema other than dbo is used, the report viewer throws the following error:

Error registering the viewer with the service

Could not find stored procedure sp_tr_GetString

I have posted a video that shows the issue.  If I use the string builder for a textbox value and select a nested property, such as DayOfWeek, for a date, then it adds:

=Fields.DayOfWeek

which fails on Preview and is wrong.  Instead it should add:

=Fields.Birthday.DayOfWeek

Please fix this.  I know that I can go type ".Birthday" to fix the issue, but it really should add the nested properties properly.

I have encountered scenarios where I want to return different results based on fields value or some expression. While I can use nested ternary operations this is not ideal as it can be difficult to read and maintain, particular for newer report designers. It would be helpful to have SWITCH and IFS statements modeled after those provided by Excel.

SWITCH would be helpful for cases where I want to check against a few different literal values and return different results.

IFS would be helpful for cases where I want to evaluate different expressions and return different results.

Modeling these after those in Excel would be sufficient, though, for more advanced cases being able to write C# code inline with the report would be helpful (will submit as a separate request).

Current version of Telerik Reporting allows to generate reports on linux environment using the gdipluslib but it doesn't support the print.

Would be nice to implement the print of the report via CUPS or IPP protocol.

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."

We are using Telerik reporting R2.2022 version in our project. Some of our reports have html link (created with tag “a”). If we preview those reports html link doesn’t act as an actual hyperlink, so it’s not clickable. We know that there is a HtmlTextBox limitation not to be interactive in WinUI report viewer. But this is important for us to be able to click on html link on WinUI and we need that functionality.  

I tested WinUI example project (CSharp.WinUIExample.VS2022.sln) and opened SwissQRBill.trdp report. The report has some links to the external source in internet, which is not clickable, but if you open it in Standalone report designer it’s clickable.  

Is it on your roadmap to implement that feature? 

Thanks,

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';`

Hi, While the Report Designer exports tags to the PDF (with Accessibility enabled), the tags exported are not fully compliant with PDF/UA or 508 requirements. For example, my document has several hundred pages, each with two or three data tables on them. While the tags get exported, they are only Paragraph tags, and NOT Table tags. Is there a way to designate Table Header Rows, Header Columns, and Data Cells in Telerik Reporting such that upon export to PDF they get tagged properly?

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)