My report has a Text Watermark as part of the PageSettings, and is configured for Accessibility. The report contains a Page Header and Page Footer. In the Page Footer, there are two TextBoxes.
When I generate an accessible PDF with Telerik Reporting and use the Adobe Reader > Read Out Loud functionality, it doesn't read the content of the second TextBox in the Page Footer.
Currently, Telerik Reporting has a dependency on Microsoft.Data.SqlClient version="5.2.2".
This version may cause build failure when restoring packages due to locked package files.
See the following dotnet issue for more information about the problem: dotnet/SqlClient#2464
Some of the Web Report Designer pop-up messages are not localizable. For example, the message about trying to access a report that does not exist on the server:

Related to:
Also affects Telerik.Reporting.Processing and Configuration: Attempt by security transparent method 'Telerik.Reporting.Processing.AssemblyRefManager.LoadAssembliesCore()' to access security critical method 'Telerik.Reporting.Configuration.ReportingConfiguration.get_Current()' failed.
I have a report with an HtmlTextBox item, which contains an ordered list(<ol>). When I export this report to PDF, and inspect the logical tree of the document with a tool like the PDF Accessibility Checker, I can see that the span with the text is inserted above the number.
As a result, when I read the document with a screen-reading tool like Adobe's "Read Out Loud" feature or NVDA, the text is read before the current number in the list, which I find unexpected.
Currently, the GetDesignerResource endpoint of the Web Report Designer service is case-insensitive, which can lead to issues if the URL is made lowercase at some point, such as by a URL rewrite rule, or similar scenarios.
For example, the following reference to the Web Report Designer script will load return the file:
<script src="api/reportdesigner/designerresources/js/webReportDesigner"></script>But if lowercase is used, for example, like this:
<script src="api/reportdesigner/designerresources/js/webreportdesigner"></script>The request will return a 404(Not Found) response.
Using Blazor native reporting component. Our underlying email sending service requires that Subject is not blank, however the UI does not validate the Subject field.
Need to be able to validate that Subject is not blank when user attempts to submit email form.
We are experiencing issues with Telerik Reporting related to RTL text (culture 'ar-JO') rendering, as outlined below:
I'm getting an error in Telerik Report Designer (Data Explorer): "Member x on type String not found"
The version is: 19.3.25.1119
Steps to Reproduce:
Please note the spelling error in the k-notificaiton-error class name. Should be k-notification-error:
<div class="trv-parameter-error k-notification k-notificaiton-error" style="">
<span class="k-notification-status k-icon k-i-x-outline"></span>
<span class="trv-parameter-error-message k-notification-content">Parameter value cannot be empty.</span>
</div>
Because of this, error messages are rendered with incorrect color (should be red):
I use the kendovalidator before rendering the report to check the correct parameter of initial and final date.
However, the validation fails because additional inputs (for the "Send Email" functionality) are included in the HTML output of the viewer even though I have disabled it.
I believe that if the "Send Email" option is disabled the mail data panel should not be created.
When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.
Additionally, images whose AccessibleDescription I have set may be read multiple times..
I had an issue with watermarks being present in the generated PDF despite the license validation passing. In the trace log, I was seeing this:
x.x.x.x.exe Information: 0 : *** ReportProcessor.ProcessReport STARTED *** x.x.x.x.exe Information: 0 : SQLite x64: v3.50.4 x.x.x.x.exe Information: 0 : x.x.x.x.exe Information: 0 : *** ProcessReport #0 "Invoice" STARTED *** x.x.x.x.exe Information: 0 : *** ProcessReport #0 "Invoice" DONE in 00:00:00.6363067 *** x.x.x.x.exe Information: 0 : x.x.x.x.exe Information: 0 : *** ReportProcessor.ProcessReport DONE in 00:00:00.7891276 *** x.x.x.x.exe Information: 0 : x.x.x.x.exe Information: 0 : License check for assembly Telerik.Reporting, Version=19.3.25.1119, Culture=neutral, PublicKeyToken=a9d7983dfcc261be: True x.x.x.x.exe Information: 0 : x.x.x.x.exe Information: 0 : *** Render Report #0 "Invoice" STARTED *** x.x.x.x.exe Information: 0 : ReportName: Invoice; DocumentName: Invoice; Extension: PDF x.x.x.x.exe Information: 0 : DeviceInfo Contents x.x.x.x.exe Information: 0 : =================== x.x.x.x.exe Information: 0 : ChangingPermissionType: "" x.x.x.x.exe Information: 0 : ComplianceLevel: "None" x.x.x.x.exe Information: 0 : CopyingPermissionType: "" x.x.x.x.exe Information: 0 : DocumentAuthor: "" x.x.x.x.exe Information: 0 : DocumentCreator: "" x.x.x.x.exe Information: 0 : DocumentKeywords: "" x.x.x.x.exe Information: 0 : DocumentNaturalLanguage: "" x.x.x.x.exe Information: 0 : DocumentProducer: "" x.x.x.x.exe Information: 0 : DocumentSubject: "" x.x.x.x.exe Information: 0 : DocumentTitle: "" x.x.x.x.exe Information: 0 : EnableAccessibility: "False" x.x.x.x.exe Information: 0 : EndPage: "0" x.x.x.x.exe Information: 0 : FontEmbedding: "None" x.x.x.x.exe Information: 0 : ForceLicenseWatermark: "True"
The issue turned out to be due to caching, but the output puzzled me while I was debugging this. Turned out `ForceLicenseWatermark` is always true (the misleading part), but only has an effect when the license validation fails.
After dragging a report viewer control from the Visual Studio toolbox to the surface of a Windows Form, the viewer is added to the component tray but it is not added to the Controls collection of the form. Thus, the viewer is not displayed when running the application.
Also, some properties of the report viewer, such as the ReportSource property, are not serialized properly after being modified through the Visual Studio properties window.
Currently, one can work around these issues by manually editing the InitializeComponent component method of the form's .Designer.cs file.