Declined
Last Updated: 29 Aug 2022 18:54 by James
Many documents have repeating information that is irrelevant and needs to be untagged, or artifacted, so that assisstive technology does not share the information multiple times. Common examples of this situation are headers, footers, page numbers, and decorative images. In most cases, it is not necessary to read these document elements on each page, so we untag the information to prevent repetition for the person reading the document with assistive technology. Is there a way to mark a report section - e.g., the page header or page footer - as Untagged or Artifacted, and have those tags be exported to the PDF? It would save a ton of time having to manually go through several hundred pages and untagging them manually.
Completed
Last Updated: 14 Sep 2022 14:34 by James
Release R3 2022

Steps to reproduce the problem:

1. Open the attached report in EUD
2. Ensure its RuntimeSettings contain parameter "EnableAccessibility" set to True or add the setting before opening the designer in its configuration file
3. Preview the report and export it to PDF


EXPECTED:
The produced PDF is tagged (accessible) - check it in Acrobat Reader's file properties in the bottom left corner. The file size should be ~155KB
OBSERVED:
The produced PDF is not tagged (accessible). Its size is ~123KB.
Unplanned
Last Updated: 19 Aug 2022 12:19 by Jyoti
When the SkipBlankPages property of the report is set to true, it throws a console error in the browser when there is no significant content in the report:
Unplanned
Last Updated: 14 Nov 2022 11:59 by ADMIN

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?


Declined
Last Updated: 25 Aug 2022 12:07 by James
Telerik Report Designer is one of the few report writing tools on the market that can export tagged PDF content. It's a major advantage of your solution. Why can it not be turned on by default, or enabled via a menu button. Better yet, how about including an Accessibility menu setting to allow for more detailed configuration of key elements?
Unplanned
Last Updated: 15 May 2025 07:30 by ADMIN
Scheduled for 2025 Q3
Currently, Telerik Report Designer cannot export the style heading level to the tag structure in the generated PDF. It exports the headings, yes, but only as a paragraph tag. This request would require that a Heading Level (e.g., Heading 1, Heading 2, Heading 3 ) field be added to the Properties panel such that a text box could be tagged as H1, H2, H3, etc.  According to accessibility guidelines, PDF/UA-1, WCAG 2.1 and 508, the tag tree needs to contain a logical reading order and tag structure. Heading Levels are essential to that. There may be only one H1 - usually reserved for the document title, then major sections get H2, subsections, H3, etc. Can this be done?
Unplanned
Last Updated: 25 Aug 2022 12:01 by James
I produce a lot of Accessible PDF documents that include many unique images - hundreds in most cases. Each image has alt text descriptions in it in the EXIF metadata of the image file itself. Most of the documents I generate a based on a one or two page template used for each record ID. The images are loaded programmatically based on the ID number for the template. Right now, with Accessibility Enabled, Telerik cannot read the image EXIF data. It would be ideal if it could be configured to pick up the descriptions already inside the image file itself. This applies to the stand alone Report Designer and the Visual Studio version.
Completed
Last Updated: 14 Nov 2024 11:02 by ADMIN
Release 2024 Q4

Currently,  you can select multiple report items with the CTRL when you run the Web Report Designer on Mac, however, this is interpreted as a right-click. Please, check the attached video.

The correct behavior should be by using CMD.

Under Review
Last Updated: 15 Aug 2022 15:41 by ADMIN

I display the WPF Report Viewer control in a closable tab. To free the resources I invoke DisposeViewerResources on tab close as described here: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/wpf-application/disposing-the-report-viewer-resources

However, I see the following dialog every time. There is no way to capture this error or suppress the dialog.

Completed
Last Updated: 14 Sep 2022 14:06 by ADMIN
Release R3 2022

Some corner case page size value force report processing to create an invalid page clipping during paging. 

Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.

Unplanned
Last Updated: 05 Aug 2022 08:57 by Joe

Please add the Web Report Designer Item Template for VB.NET projects too

Unplanned
Last Updated: 04 Aug 2022 09:17 by Wayne Hiller
There seems to be no way to create a Style Rule with Style Selector in the Web Designer. The only option available is Type.
Unplanned
Last Updated: 04 Aug 2022 09:08 by Shannon
Created by: Shannon
Comments: 0
Category: Reporting
Type: Feature Request
1

Consider adding functionality that allows for loading Assets into the Asset Manager from code. 

I would prefer to store assets in a database and load them up for a user.

Makes more sense than randomly loading them from whatever computer you are working on.

Unplanned
Last Updated: 04 Aug 2022 07:24 by Doyeong
The SVG image from a PictureBox is displayed cut in the Html Viewer. When exporting to PDF it is fully shown.
Declined
Last Updated: 10 Aug 2022 08:30 by ADMIN

I am trying to get a basic example of the Web Report Designer working following the guide here but I keep getting this error message

in the console, I can see these errors

here is the razor page that contains the WebReportDesigner

@page "/report-designer"

@attribute [Authorize]

@using Telerik.WebReportDesigner.Blazor

<WebReportDesigner DesignerId="wrd1"
                   ServiceUrl="/api/reportdesigner"
                   ToolboxArea="new ToolboxAreaOptions() { Layout = ToolboxAreaLayout.List }"
                   PropertiesArea="new PropertiesAreaOptions() { Layout = PropertiesAreaLayout.Categorized }" />

Any assistance would be appreciated

Under Review
Last Updated: 09 Aug 2022 14:24 by ADMIN
Created by: Stewart
Comments: 1
Category: Reporting
Type: Feature Request
5

I am currently investigating including the Telerik Reports in our products but when I load the Web Report Designer it loads a theme which is overwriting our custom theme. 

Is there any way to prevent this so that we keep our custom theme?

Unplanned
Last Updated: 01 Aug 2022 06:57 by Dominik
Please add a workspace preferences option to not save the report when Preview is initialized in the Web Report Designer
Unplanned
Last Updated: 26 Jul 2022 08:10 by Dominik

If you add the 'kendo.common.min.css' that is required for the Html5 Viewer to the page with the Web Report Designer, the latter Menu styles get broken.

Due to this, if you need to have both the viewer and the designer in the same project and cannot have scoped styles, the appearance of one of them will be broken.

Unplanned
Last Updated: 18 Jul 2022 08:20 by Todor

In some scenarios, it would be helpful to have the path to the report available, for example, as a Global Object, so that you may use it in the Expressions.

Here is a use case. The PictureBox resolves relative paths with respect to the report's folder. Currently, if you want to check whether an image that is in the report's folder exists by its name only, you need a custom user function. If you know the report's folder, you may do this with System functions.

Unplanned
Last Updated: 15 Jul 2022 08:21 by Blair
Created by: Blair
Comments: 0
Category: Reporting
Type: Feature Request
1

In some cases, the textbox width will be nearly but not enough to fit the whole string and as a result, the textbox will grow and will thus push the items below it further down.

In Page Sections, this may even result in some of the items that are near the bottom not being displayed at all.

It would be great if there was a warning when the width is not enough so that such scenarios are avoided.

There should also be an option to disable the warnings.