We have reports that contain a table of images. This seems to work great in the designer and when generated to a PDF without accessibility turned on. However, with accessibility turned on and rendering to a PDF, it throws an exception:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.TryAttachToParentNode(ProcessingInstanceIdentifier id, PdfOrderedReference element, Int32 rowIndex, Int32 columnIndex)
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.TryAttachToParentNode(IProcessingElement processingElement, IProcessingElement parentProcessingElement, PdfOrderedReference taggedElementReference)
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AttachNonLeafNode(LayoutElement element, PdfOrderedReference taggedElementReference)
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.InitTaggedElement(AccessibilityPdfElement pdfElementType)
   at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AddFigureElement(ITableCell element)
   at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
   at Telerik.Reporting.Writing.AccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
   at Telerik.Reporting.Writing.VisualElementWriter`1.StartWriteAccessibilityItem(ReportItemBase item, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.VisualElementWriter`1.WriteClientFocusableItems(T element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.ReportItemBaseWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.ElementWriter`1.Telerik.Reporting.Writing.IElementWriter.StartWrite(LayoutElement element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(PictureBox pictureBox)
   at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
   at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
   at Telerik.Reporting.Paging.PageElementsLayer.OutputToPage(IPageHandler handler)
   at Telerik.Reporting.Paging.PageContent.Output(IPageHandler handler)
   at Telerik.Reporting.Paging.PageCompositionBase.OutputPageContent(Stopwatch stopwatchOutputContent, PageContent pageContent)
   at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass124_0.<CreatePageContentOutputTask>b__0()

In the attached report, all items in the detail section have Docking set to Top.

In the Interactive view of the report designer, the report looks fine.

In PrintPreview mode though, some items overlap.

There is an issue in .NET 9 when using a mounted network drive. When resolving reports, I get the following exception:

The issue seems to be related to a regression introduced in .NET 9:

• For a network drive, System.Windows.Forms.Application.StartupPath returns a path with \?UNC\ prefix
• Work with 'Mounted Network Drive' in .NET 9.0

Consider finding a way to work around this issue.

I pass the value of an Integer Report Parameter as '11000000000000003' from the viewer's setup. In the viewer though it appears as 11000000000000004. The wrong value 11000000000000004 is seen also in the 'parameters' request passed from the viewer to the service.

The issue is reproducible in the HTML5 Report Viewers and in the Blazor Native Report Viewer.

Currently, TIF images cannot be selected as pictureBox values from the file dialog of the Standalone Report Designer. However, the documentation states that it is a supported image format:

• PictureBox Report Item Overview

I have a .NET Framework 4.7.2 ASP.NET MVC project.

I am currently on Telerik.Reporting 19.0.25.211. I also have Telerik.Licensing package 1.4.10 installed on the project.

After upgrading my project to Telerik.Reporting 19.0.25.313, without touching the licensing package, in my .csproj file I'm seeing Telerik.Licensing.Runtime reference is set to 1.4.6.0, although the nuget package manager says that I have 1.4.10 installed.

In the project References also appeared a reference to the old Telerik.Licensing version after the update.

The property UserIdentity.Current is decorated with a [ThreadStatic] attribute, that guarantees a new instance will be created per each thread, when used in a synchronous context.

In asynchronous context, e.g. when an await operation is performed, the current thread is released, and another thread from the thread pool may take over. This can lead to the UserIdentity being overridden or conflicting with another request.

The RTF rendering automatically switches to the Tables rendering mode whenever a Crosstab/Table/List is detected in a report. This rendering mode throws an exception whenever the report contains PictureBox with one of the following sizing options.

• Center
• Normal
• Stretch
• ScaleProportional

The RTF export should work with all PictureBox sizing options regardless of the rendering mode.

To work around the issue currently, one can either force the rendering engine to use the Frames rendering mode using the RenderingMode device information property or set the Sizing property of all picture boxes in the report to AutoSize.

If I render a report that includes a HtmlTextBox item with line breaks in its value(<br />) to PDF with the Skia graphics engine and a font such as DejaVu Sans, the <br /> tags are rendered as squares.

Sample HTML:

<p>line1<br />line2<br /><i>line3</i></p>

Using a font such as Arial, there are no such issues. However, before 2024 Q4, it wasn't a problem when using the DejaVu Sans font as well.

If I render a report that produces zero pages in the Native Angular Report Viewer, the rendering will fail with an exception in the browser console but it won't be caught by the viewer's error event.

This exception breaks the report document generation and it should be caught by this event according to the Handle errors in Telerik Reporting - Telerik Reporting article.

Hi,

I've attached the following abstraction that I made which renders pdfs using a TRDP file.

In an environment where we're bulk generating documents, this falls over as the returning code can return documents from other threads.

This solution is fixable by adding in a lock (commented out in the example), but it degrades the performance quite a bit and users wouldn't expect this behaviour.

This has been reported previously: https://www.telerik.com/forums/is-the-reportprocessor-renderreport-function-thread-safe

I'm using the 2025.1.205 NuGet Packages.

Regards,

Hayden

After updating to Telerik Reporting v19.0.25.211, the relative path provided to the UriReportSourceResolver is no longer working.

For example, I used to provide only the name of the directory with the reports(e.g. "Reports") to the UriReportSourceResolver, and if there was such a subdirectory inside the project's base directory, the reports were successfully resolved.

This is no longer the case with v19.0.25.211. With this version, I have to provide the absolute path to the "Reports" directory for it to work.

If I put the following content in an HtmlTextBox, when I open the preview mode of the designer or look at it in the Html5 Report Viewer I get annoying extra gaps:

<p>Comment</p><p>Comment</p><ol><li>List</li><li>List</li><li>List</li></ol><p><br></p><p>Comment</p><p>Comment</p>

I tried to replace these <p>-tags with <div>-tags:

<div>Comment</div><div>Comment</div><ol><li>List</li><li>List</li><li>List</li></ol><div><br></div><div>Comment</div><div>Comment</div>

It helps. But there are some other tags that cannot be replaced (tags of ordered and unordered lists for example). And these gaps are still rendered. 

I followed the instructions from the Loading .NET 9 assemblies in the Standalone Report Designer for .NET - Telerik Reporting article to use the Standalone Report Designer for .NET with the .NET 9 runtime so that I can load .NET 9 assemblies in it but it crashes on startup: