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.
I use the exportBegin event to prevent the default export logic. However, when I do that, the default viewer notification remains, and I have to hide it manually:
exportBegin: function (e, args) {
args.handled = true; // Set to true to cancel the default export behavior.
//...
$(".trv-notification").addClass("k-hidden");
},
Double-click selection in the expression editor isn't context-aware. In almost every other application, double-clicking selects a token based on its surrounding context — a single field/identifier when clicking on a field, or the word boundary within a string literal when clicking inside quotes. The expression editor doesn't respect these boundaries, so its double-click behaviour is inconsistent with the standard expression-editor behaviour users expect.
Expected: Double-click selects the relevant token based on context (e.g. an individual field reference, or a word within a string literal).
Actual: Double-click selection ignores context and does not match the token/word-boundary behaviour found in virtually all other expression editors and text inputs.
I have graphs in my report. I render them with Skia on Linux. The issue reproduces with Skia on Windows as well.
The legend labels are not aligned well with the color icon, and data labels on a horizontal bar chart (with OutsideEnd) are misaligned as well:
If I open the expression dialog in the Web Report Designer and select one of the available functions, I will see a sample snippet in the third column below the expression area.
This column is not selectable, so I cannot copy the example and test it out. This example should be copyable, so that each function can be easily tested in the report designer.
I have localized a report with a Graph in the 'ar-SA' culture.
When exporting to PDF from the viewer, the report is generated as expected. In the Report Viewer's Preview, though, the Graph Legend and Labels are not correct:
I am using Native Blazor Report Viewer, but the problem also reproduces in the HTML5-based web viewers, with all the themes I have tested.