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

Sometimes I need to be able to allow the users to choose not only the date but the time as well when displaying DateTime report parameters in my reports. There is no out-of-the-box functionality to achieve this and I am forced to implement custom parameter editors -  Creating and Using Custom Parameter Editors in HTML5 ReportViewer - Telerik Reporting.

I should be able to set whether a DatePicker or DateTimePicker widget should be used for DateTime parameters from the report viewer's initialization options, such as how I can change the editor for single/multi-value parameters in the HTML5 report viewers - HTML5 Report Viewer Options Overview - Telerik Reporting.

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.

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.

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.

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 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.

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.

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.

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()

To reproduce, use online web designer demos with Employee Sales Summary.trdx report.

Check the video https://go.screenpal.com/watch/cTfDlNnj4I1.

1. The main report opened in the designer has a Navigate to Report action.
2. Preview the report and trigger the action to open the second report.
3. Now, click on Design to go back to design time.

Expected: opens the main report

Observed: In design you see the second report

Additionally, the URL to the second report is absolute rather than relative path - the issue logged in Full system-path being used by REST Service as reference when linked by a 'Navigate To Report' action

Currently, when using External Stylesheets in the reports, the engine tries to first load the stylesheet as an embedded resource of the assembly. If it fails to load it from the assembly, a message is written to the trace along the lines of:

ESS: Attempt to load ExternalStyleSheet from EmbeddedResource from assembly Telerik.Reporting, Version=19.0.25.211 with resource name styles.xml is unsuccessful.

After this, the engine will try other ways to resolve the stylesheet such as from URI and if it succeeds, the report will render as expected.

This can create confusion because looking at the trace, one might think that there were errors with the rendering of the report because the stylesheet did not load but it was actually successfully loaded with one of the other approaches.

It would be better to write the errors to the trace only if the stylesheet does not load after all attempts.

Hello Telerik Team,

I would like to suggest a feature enhancement for the Web Report Designer that would allow dynamic configuration of design-time parameter values during initialization.

Currently, design-time values for report parameters are embedded within the report definition and can only be set manually using the Web Report Designer interface. While runtime parameter values work perfectly and can be passed dynamically through code, not being able to dynamically set design-time values causes significant limitations—especially during the report design process.

My Use Case:

In my application, I load data from a dynamic web service endpoint, and the service domain needs to be set at runtime. While this works fine during preview in my ASP.NET MVC project (where I pass the URL dynamically using report parameters), I run into issues when designing reports:

• During design time, the URL has to be manually entered into every Web Service Data Source just to fetch the model fields and avoid errors.

• If the domain name changes (e.g., due to staging/production environments), I must manually update the domain in every report and each Web Service Data Source, which is both time-consuming and inefficient.

• This becomes even more tedious in large projects with many reports and data sources.

So, my question is: Is it mandatory to pass design-time values (like the service URL) manually just for design-time purposes? If not, it would be incredibly helpful to have a way to supply these values dynamically during the Web Report Designer initialization, perhaps via a configuration option or external context.

Petar from the Telerik team mentioned that this would indeed be a valuable feature and encouraged me to submit this suggestion. You can view our discussion here: 🔗 Dynamic Web Service Domain Configuration in Telerik Report Designer Server

This capability would make designing reports much smoother and far more maintainable, especially for applications that rely on dynamic, environment-specific configurations.

Thank you for considering this request, and I appreciate your continued support and guidance.

Screenshots are also attached for quick reference, though they are already available in the forum link above.

Best regards,
Prabesh

When I export my report in Excel with the Standalone Report Designer for .NET,  the GDI engine produces the expected result, whereas with the Skia graphics engine, the Graph in the report is rendered with a bold font, although I use a regular/normal font.

When upgrading my .NET Framework project with the Upgrade Wizard, the Telerik.Reporting.OpenXmlRendering assemblies, including the newer 2.7.2 and 3.0.1 ones, are not upgraded

All assembly references except Telerik.Reporting.OpenXmlRendering ones are updated. The upgrade wizard finishes without errors.

This is very annoying as I have to replace them manually,

When using a date parameter with AutoRefresh set to True in the Standalone Report Designer, selecting a new value from the date picker does not automatically refresh the report viewer to show the updated report. To make the new value take effect, you need to move the focus away from the date picker.

I have the chance to use a 27", 5120 x 2880 monitor, with text on Windows set to 200%.

The problem with Telerik Report Designer is that the icons in the report designer are very small and barely usable:

- Panel icon to move it.
- Table icon to move it.
- The open / close icons in the Report Explorer.

Also the zoom indicator at the bottom left of the screen, where the text part is too small to display the current zoom.

 I cannot create a Report Parameter with the same name as a data source parameter or CSV data source field. Trying to do so results in an error messagе

(Error Could not change property 'Name'. Name 'FromEffectiveDate' already exists).

This issue can be demonstrated in the Web Report Designer Demo page: create a parameter for the yearDataSource data source, try to create a report parameter with the same name to get the error.

Using report parameter names that are also data source parameter names works fine in the Standalone Report Designer.