The Telerik.Reporting documentation mentions that the Telerik.Reporting.* libraries should be available on nuget.org with the most recent release. However, when I search for Telerik.Reporting in the NuGet Gallery, I am not able to find any Telerik.Reporting.* package. The other products we use (UI for WPF, Document Processing) seem to be available though.
-----------------------------------------
Staff note: On the Reporting side, our initial goal was indeed to make Telerik Reporting available through nuget.org, alongside the rest of the Telerik product portfolio. However, we are currently investigating an issue that is preventing us from publishing the Telerik.Reporting packages to nuget.org, which has delayed their availability.
Please use this feedback item to subscribe to updates and receive a notification as soon as the Telerik.Reporting packages become available on nuget.org.
I have created a report group, and in that group's header, I have added a textbox with a sorting action.
The action can be triggered, but the data does not get sorted, regardless of whether the sorting target is the report itself or the group from which the group section is created.
When the reports are displayed within the WPF Report Viewer, they are rendered in the XAML format, and it does not natively support SVGs.
Currently, the SVGs are always rasterized before being written to the XAML, which results in the images being blurred when zooming in the report viewer.
When I enable accessibility in my reports, the final PDF document becomes 20+ times bigger than without accessibility. The reports contain large amounts of data and result in 2000+ pages.
I need the images in my reports (usually only one logo) to have alternative text, so the screen readers can describe them. To achieve this, currently I have to enable accessibility for the entire report, hence the huge final documents.
It would be very useful for my scenario to add alternative text to the PictureBox without declaring the entire report as accessible.
I am using the HTML5 report viewer and seeing 4 errors in the WAVE tool, along with multiple alerts. See: https://wave.webaim.org/report#/https://demos.telerik.com/reporting/product-sales
Please consider addressing them.
Currently, the Download Raw Data action is available in the Windows Form Report Viewer. It is hard-coded there, and the download button appears when you hover over the data item.
The developer can cancel the action through the interactive action event handlers. However, the button persists even when the action is cancelled and doesn't do anything, which is misleading and confusing for the report readers.
Please let the developers disable the action/button, for example, through configuration in the viewer.
We get an incorrect “Email format is not valid” validation when sending a report to multiple recipients. We are using the wrapper/HTML5 Angular Report Viewer
In the To field, enter multiple valid email addresses, for example:
user1@example.com,user2@example.com
or
user1@example.com;user2@example.com
I am using the Standalone Report Designer for .NET to open a code-based report from an application that was migrated from .NET Framework. Before the migration, function calls defined in the designer.cs file were preserved and evaluated at runtime as expected. However, after migrating to the code-based reports functionality supported by the Standalone Report Designer for .NET, these function calls are evaluated immediately during the report import process, and the resulting values are then serialized and stored in the report definition.
It would be nice if the function calls were preserved in the imported report, allowing them to be evaluated later at runtime, as their return values may change depending on the execution context.
Currently, graph axes do not provide a way to render separator lines between category groups. While this is generally not an issue for simple scenarios, it can make charts with nested categories difficult to read.
For example, when a graph displays multiple subcategories under a parent category (such as revenue ranges grouped by quarter), there is no built-in visual indicator showing where one parent category ends and the next begins.
It would be useful to provide support for category separators on graph axes, allowing report authors to visually separate category groups and improve readability when working with hierarchical data.