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.
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).
Hi Team,
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).
Thank you,
Maks
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.
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.
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.
https://www.telerik.com/forums/missing-or-invalid-parameter-value-please-input-valid-data-for-all-parameters
What's the long-term plan for supporting Linux and Telerik Reporting? The dotnet design team is looking to remove support for System.Drawing.Common on Linux platforms. They're recommending compiler warnings in .Net 6, and full PlatformNotSupportedExceptions in .Net7
Sources:
designs/system-drawing-win-only.md at main · dotnet/designs (github.com)
Breaking change: System.Drawing.Common only supported on Windows - .NET | Microsoft Docs
Currently the behavior of the Web Designer and Standalone Designer is different in regard to DateTime Report Parameters and its "Kind" property.
The Web Designer will assume the value is of Kind "Utc" and the Standalone Designer uses "Unspecified".
This recently became more of an issue since the newer PostgreSQL Provider versions are a lot more strict regarding the "Kind" property:
Npgsql: Timestamp rationalization and improvements
The consequence of this is not being able to use Sql parameters which will work in both the WebDesigner/WebViewer and the StandaloneDesigner:
To resolve this issue right now, one would need to resort to ugly workarounds:
To properly address this issue it needs to be possible to set the Kind property in the Viewer. Or at least the behavior between the WebDesigner and Standalone Designer should be the same.
Additionally/Alternativly it should be possible to set the target Kind in the Report Parameter.
With kind regards,
Dominik Rothert
This is not a clone. It's a new request I had to add, since the old was closed with a technically fault answer. By technically fault I mean possible, but in real scenario unusuable. F.e Jasper's SubReports have a property called DataSource. The sub-reporst uses this dataSOurce for rendering it content. The DataSource is always set on the Main report. Everything via designer, no need for coding. So I'd like to see such a possibility in telerik reports. The suggested solution - with the bindings http://www.telerik.com/forums/how-to-bind-the-datasource-of-a-subreport-in-the-designer is technically wrong. It assumes that the child report knows at which level he resides inside the main report. The child report (or it's binding) should have not such info embedded. Let's see on an example. Let's have a dataset: User.Address User.PostalAddress User.Wife.Address User.Wife.PostalAddress The dataset should be bound to the main report. The main report should have 2 sub-reports (address and postal addres). It can have an another sub-report (for wife data) which then would again have 2 sub-reports inside for addresses. Using the technically wrong solution, the addresses for the main user should have a binding expr. like: =ReportItem.Parent.DataObject.xy and the wife's addresses have like: =ReportItem.Parent.Parent.DataObject.xy There is a big problems with such a binding: the child must know the hierarchy of the data. The technically clean solution is to have a dataset assigned to the main report. When adding a sub-report to the main report, via binding we should set the new data-source for the sub report. something like: MainReport.Data = dataSource. SubReportAddress = dataSourceOfTheCurrentReport.Address. SubReportWife = dataSourceOfTheCurrentReport.Wife and inside "wife report" the next sub-report for address address should have a binding again like: SubReportWifesAddress = dataSourceOfTheCurrentReport.Address
Coming from having developed many SSRS reports one thing I think telerik is missing is a nicer visualisation of row and column grouping in a table. SSRS does this really well as shown in the screenshot below where we can easily see which rows belong to the detail and 2 other groups.
I think this would be a very useful addition to the telerik designers!
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.
Our clients enter information using the radeditor and in many cases want to embedded tables and graphics into their text. Using your reporting tool there is no way to print this information. I know you have suggested using your table and image tools, but that doesn't work when you are dealing with freely formatted text so the existance and location of the tables and images cannot be predicted.
Add progress bar that indicates when the report would be fully rendered.
Hi Team,
I know it's a bit early to be asking for this, but I wanted to get a feature request on the backlog so it's trackable.
Currently, you already have a ReportViewer for WinUI3. This means you have a good head start for a ReportViewer that can be used in a .NET MAUI project and have native Windows support.
I'm mostly concerned about having support on a Mac, not the mobile platforms. So if you can build a MacCatalyst ReportViewer, you can cover a good portion of developers who are hoping MAUI can give them desktop support across platforms.
Thank you,
Patrick
Tip: If you use SkiaSharp or Maui.Graphics for rendering, you can get automatic cross-platform support everywhere for free