Hi, While the Report Designer exports tags to the PDF (with Accessibility enabled), the tags exported are not fully compliant with PDF/UA or 508 requirements. For example, my document has several hundred pages, each with two or three data tables on them. While the tags get exported, they are only Paragraph tags, and NOT Table tags. Is there a way to designate Table Header Rows, Header Columns, and Data Cells in Telerik Reporting such that upon export to PDF they get tagged properly?

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.

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

Steps to Reproduce

1. Open any report in the Telerik Report Viewer.
2. Click Send Email.

3. In the To field, enter multiple valid email addresses, for example:

   user1@example.com,user2@example.com
   

   or

   user1@example.com;user2@example.com
   

4. Click Send.

Actual Result

• The validation message "Email format is not valid." is displayed beneath the To field.
• Despite the validation error, the email is sent successfully to all recipients.

Expected Result

• Multiple valid email addresses should be accepted without displaying a validation error.
• Since the email is successfully delivered, no validation message should be shown.

I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.

It would be very useful if we could copy/paste Report Parameters between reports.

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.

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");
                    },

When a report is saved in the Web Report Designer, a popup appears confirming that the report was successfully saved. However, it is visible for far too long and blocks users during this time.

This feature request is to add an 'ok', 'hide' or 'close' button to these types of popups so the user can dismiss it.

Thank you,

Shannon

Hi there,

Adding an external style sheet to a report in a report-book triggers an error when previewing the report book, "Object reference not set to an instance of an object" 

I've attached the bare minimum project to reproduce the error.

I've also tried upgrading to R3 2020

Cheers

In my Graph, I have set the AccessibleRole and AccessibleDescription. The alternative text is read correctly by the Acrobat Reader's 'Read out Loud' functionality.

The problem is that it keeps reading it multiple times.

The HTML5-based report viewers send 404 request to `/sass/fonts/kendo-font-icons.ttf` when font icons are being used:

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.