When I have multiple reports open in the Standalone Report Designer, I am not able to rearrange/reorder them.

Refer to the tab behavior in Visual Studio, where you can drag one tab and move it to be in front of another tab.

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.

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?

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

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.

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.

It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.

If you have a lot of graphs in your report then it is more convenient to change the color palette one place.

The attached sample has a simple table with two row groups, and "header" rows created via "Insert Row -> Outside Group - above".
The groups have "keep together" set.

But despite this, the header rows render at the bottom of one page, with data rows on the following page. This should never happen, I can't think of any case it would be expected (it would be like having "Chapter 2" at the bottom of a page when the text for it starts on the next page). 

I also have a sample with just 1 row group, but with 2 detail rows, and the same thing happens. It only appears to work when there's just 1 row group and 1 detail row.

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.

We have spotted that PInvoke is now marked as deprecated (this applies even to the latest 0.7.124 version). In the description of the PInvoke.User32 NuGet package, it is mentioned that Microsoft.Windows.CsWin32 should be used instead:

Please consider replacing the deprecated package.

Currently, if I want to see what the device info settings for an extension like the PDF are, I need to open the documentation - Telerik Reporting Configuring the Output Formats PDF Device Information Settings - Telerik Reporting, then copy the setting that I wish to use in my code.

It would be easier and safer if the device information settings for each format were exposed as a public enum/class. On that note, it would also be easier if the available formats were exposed as well, instead of manually typing them. For example:

public static classTelerikDeviceInfoSetting
{
    public static class PDF
    {
        public const string DOCUMENTTITLE = "DocumentTitle";
        public const string DOCUMENTAUTHOR = "DocumentAuthor";
        public const string DOCUMENTSUBJECT = "DocumentSubject";
        public const string DOCUMENTPRODUCER = "DocumentProducer";
        public const string DOCUMENTCREATOR = "DocumentCreator";
    }

    public static class XLSX
    {
        public const string USENATIVEPAGEHEADER = "UseNativePageHeader";
        public const string USENATIVEPAGEFOOTER = "UseNativePageFooter";
        public const string SHOWGRIDLINES = "ShowGridlines";
    }
}

public static class TelerikRenderingExtension

{

public const string PDF = "PDF";

public const string XLSX = "XLSX";

}