Currently the generated accessible PDF documents contain tagged elements, but lack information about the logical structure of the PDF document. This prevents screen readers of correctly reading the PDF document contents. The tools like PAC (PDF Accessibility Checker) do not display correctly the document structure.
When Kendo version 2023.1.314 is used, the tooltips of the HTML5 Report Viewer and its wrappers flicker when the cursor hovers above them.
Telerik Reporting Version: 188.8.131.525
I have a JsonDataSource that contains a Base64 string field I want to use in a PictureBox.
When I drag the field from the Data Explorer in the Report Designer, it creates a TextBox with the text content. When I run the report, there is an error "A generic error occurred in GDI+'.
Consider creating PictureBox when dragging a Base64 string instead of TextBox.
At the moment it's only possible to have your reports in old-fashioned projects.
It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).
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).
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.
I need to know when one of my users has canceled the rendering of the report in order to update the UI accordingly.
Please consider firing a 'renderingCanceled' event when the above occurs or passing an additional parameter to the updateUi event to specify the rendering state.
As a developer, I need to be able to align an image that is scaled proportionally in top-left for example, so that it looks more aesthetic and as required from the clients who use for example logos of various sizes. I.e., my expectation is that I should be able to specify both "Scale Proportional" AND Image Alignment, both horizontal and vertical.
The attached 'Test.svg' image markup file contains 'use' statements that lead to duplicating part of the image parts when rendering the report in PDF.
The other file in the archive, 'Test-noUsings.svg' is the same image without 'use' statements and doesn't have this problem.
If the CanGrow property of a TextBox/HtmlTextBox is set to True and Left and Right Anchoring is applied, the Height of the text box will be determined based on its design-time Width.
Thus, even if the actual final Width of the item is enough to fit its contents on a single row, the text box can have a larger than necessary Height.
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 designing reports with lots of parameters (which is very common for my usage), I often get error message "Missing or invalid parameter value" or "Syntax error in expression". I find it very time consuming and annoying to manually check "all" parameters in order to identify which one is causing the issue.
Would it be possible to include more details in these error messages, e.g. by including the name of the (first) incorrect parameter? Preferably for the message in report viewer / preview, but at least in the log file.
While some viewer options such as the pageMode, viewMode, etc. are already exposed and configurable through code, the parameters are not. This means that the viewer will always load the report with the default report parameter values which can troublesome.
For example, I need to be able to pass a JWT to a WebServiceDataSource inside my report and I use a report parameter for doing so. This works as expected when I use a simple report viewer but when the report is loaded by the Web Report Designer, it is not possible to pass a value from the front end where the designer is initialized.
Currently, the ReportDesignerControllerBase class does not enforce its own JsonSerializerSettings, rather it uses the ones set globally, on the application level. This could potentially lead to errors since the Web Report Designer requires the data to be serialized in camelCase. When PascalCase is used, certain functionalities get broken.
A way to avoid this would be to explicitly define JsonSerializerSetting in the ReportDesignerControllerBase class so that the Report Designer service does not break regardless of the setting defined on the application level.
When rendering a report with a Graph on Linux, the labels of the Graph are not aligned properly.
For example, right-aligned labels are offset to the left depending on the content and length of each label.