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.

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.

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.

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

If I have set up cascading report parameters, the dependant parameter's value is evaluated before the data source is updated.

This can cause issues when complex expressions are used to set the value since the values of the fields won't be accurate.

For example, if I use a DateTime parameter and need to add minutes to the date based on a field from the data source, and the data is filtered based on the value of another report parameter, I have to use the IsNull() function to avoid providing a null value(because the field will be null before the data source is re-evaluated):

= AddMinutes(Today(), IsNull(First(Fields.IntervalMinute), 0))

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:

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.

Currently, there is design-time support for the WinFoms Report Viewer in the VS Designer only when the project targets .NET Framework.  I need this functionality to be supported in .NET WinForms projects as well.

In some cases, the engine will not render the graph and will instead display the message 

The current NumericalScale settings would result in more than 1000 labels which will make the scale unreadable. Please set the axis/ grid lines visibility to False or change the corresponding property.

The reason to see this or similar messages is that the selected LabelStep, MajorStep, or MinorStep scale property has a value that is too small and the processing engine will violate the previously mentioned constraint numbers.

The issue is fixed by manually correcting the values for those properties but I wish that the automatic configuration would be better.

When there is a combination of Arabic and English text in any control and if the font family is set to "Calibri", exporting to PDF results in the following error in the stack trace:

Telerik.ReportDesigner.exe Error: 0 : System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Documents.Fixed.Fonts.OpenType.Tables.MultipleSubstFormat1.Apply(GlyphsSequence glyphIDs)
   at Telerik.Documents.Core.Fonts.OpenType.Tables.Lookup.Apply(GlyphsSequence glyphIDs)
   at Telerik.Documents.Fixed.Fonts.OpenType.Tables.ChainedSequenceContextFormat3.ApplySubstitution(GlyphInfo glyphInfo)
   at Telerik.Documents.Fixed.Fonts.OpenType.Tables.ChainedSequenceContextFormat3.Apply(GlyphsSequence glyphIDs)
   at Telerik.Documents.Core.Fonts.OpenType.Tables.Lookup.Apply(GlyphsSequence glyphIDs)
   at Telerik.Documents.Core.Fonts.OpenType.Tables.Features.FeatureInfo.ApplyLookup(Lookup lookup, GlyphsSequence glyphIDs)
   at Telerik.Documents.Core.Fonts.OpenType.Tables.LangSys.Apply(GlyphsSequence glyphIDs)
   at Telerik.Documents.Core.Fonts.OpenType.OpenTypeFontSourceBase.ApplySubstitutions(UnicodeRange range, List`1 glyphInfos)
   at Telerik.Documents.Core.Fonts.OpenType.OpenTypeFontSourceBase.TryGetGlyphIds(String text, UInt16[]& glyphIds)
   at Telerik.Reporting.Pdf.PdfFontDictionary.AddChars(String text)
   at Telerik.Reporting.Pdf.Rendering.PdfRenderer.DrawString(String text, PdfFont pdfFont, IBrush brush, RectangleF rect, Boolean rightToLeft)
   at Telerik.Reporting.ImageRendering.CanvasPdf.DrawRegularChunk(String text, StringChunkContext context)
   at Telerik.Reporting.ImageRendering.CanvasBase.DrawStringMultiline(String s, StringChunkContext context, Boolean isFinalTextChunk)
   at Telerik.Reporting.ImageRendering.DocumentBase.WriteText(String text, RectangleF bounds, IFont font, Color foreground, TextFormat format, MatrixBase transform, Boolean isFinalTextChunk)
   at Telerik.Reporting.Writing.TextBoxWriter.WriteContent(DocumentWriter writer, TextBox textBox, ElementPageInfo pageInfo)
   at Telerik.Reporting.Writing.ProcessingContentElementWriter`1.WriteElement(T element, ElementPageInfo pageInfo, DocumentWriter writer)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(TextBox textBox)
   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()

If we change the font family to "Arial" the report is exported to PDF correctly.

My report contains a Crosstab with HTMLTextBox. When exporting to PDF, the document looks fine.

In Word export, the HTMLTextBox content is partly hidden and shows only when I manually extend the corresponding item height.

We use some cascading/dependant parameters and, in some cases, these have their "value" property (initial/default) value unset, generally to prevent the viewer auto-run as well as to give the user a chance to select first.

The dependant parameters have their Value properties set to the ValueMember field(e.g. =Fields.value) so when the cascading parameter is selected, the dependant will have a valid value set.

However, the "missing or invalid parameter" still shows that the dependant parameter has an invalid value.For example:

In the WebReportDesigner, when resizing a table cell on the designer-Element (NOT through the properties area), the Units of width and height are always reset to pixel.

The selected unit should not change when resizing the table cell/column/row.