The print functionality cannot be used in Google Chrome 77.0.3865.75 (lastest update). The following error is displayed in the console of the browser: Resource interpreted as Document but transferred with MIME type application/pdf.
As an alternative, you can use other web browsers for printing.
Hello Telerik team!
In the attachment, there are two PDFs, generated by the same template (also in attachment): one built under Windows, another one - under Linux (Docker). See red boxes as defects on the screenshot:
Dockerfile fragment:
# MS TrueTypeFonts install
RUN wget http://ftp.de.debian.org/debian/pool/contrib/m/msttcorefonts/ttf-mscorefonts-installer_3.6_all.deb -P ~/Downloads
RUN apt install -y ~/Downloads/ttf-mscorefonts-installer_3.6_all.deb
RUN apt-get install -y libc6-dev
RUN apt-get install -y libgdiplus
RUN apt-get install -y libx11-dev
RUN rm -rf /var/lib/apt/lists/*
Please help us to resolve these issues in Linux.
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" />
Due to breaking changes related to the Kendo state classes - https://docs.telerik.com/aspnet-core/styles-and-layout/components-rendering-overview#state-classes, report parameters loaded in the HTML5 Report Viewers that use the ListView widget, are not selected properly, thus the report is not updated with a new report source and the data does not change.
When trying to set the 'parametersAreaVisible' option in the Angular viewer the application breaks with an error in the browser console:
"Can't bind to 'parametersAreaVisible' since it isn't a known property of 'tr-viewer'."
The default value of the report property SkipBlankPages is True and when there is an error in the report, for example, due to a problem with the connection to the database, the error message may be hidden as the report is not rendered at all.
The report should be rendered in order to display the error message also when SkipBlankPages is True.
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 fix to the bug TOC page numbers and total PageCount are incorrect in some scenarios provided in R2 2023 may have led to another bug, as when I render my report with TOC the total page count is not correct in PrintPreview, although the page number is correct.
For example, on the last page, I see page 126 out of 123.
I am preparing report having Arabic and English text.
In the Standalone Report Designer for the .NET Framework, Report Preview and exported documents, including PDF are fine with R3 2023 and older versions from 2023.
When I render the same report in PDF in .NET 7 WebApi or with the .NET 6 Standalone Report Designer with R3 2023, the Arabic text is broken. The same look as expected with R2 2023 SP1 and previous Reporting versions.
When a Report with ObjectDataSourceParameter is loaded into the WebReportDesigner, the designer throws an error when trying to initialize the parameter.
Could not create instance of 'ObjectDataSourceParameter'. TypeError: Cannot read property 'push' of undefined
at new d (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:89908)
at new a (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:277743)
at s.CreateInstance (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:644848)
at d.<anonymous> (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:515470)
at Generator.next (<anonymous>)
at http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:513964
at new Promise (<anonymous>)
at l (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:513709)
at d.CreateComponent (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:515160)
at a.<anonymous> (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:58884)
The Upgrade Wizard throws an error when upgrading projects containing reporting-related JS/CSS/etc. report viewer files. For example:
Could not find file 'C:\Program Files (x86)\Progress\Telerik Reporting R3 2023\Html5\ReportViewer\js\telerikReportViewer.kendo-17.2.23.1010.min.js'.The files in question are present in the expected directory but they no longer have the version number suffix in their names ('-17.2.23.1010' in the example above). Copying the files and adding the suffix to the copies resolves the issue.
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."