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.

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,

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.

If I use an HTML5-based Report Viewer with the default CONTINUOUS_SCROLL page mode and I start scrolling to the next page, the Get Document Page request is made multiple times for the same page.

If I move to the next page via the toolbar buttons or if I use the SINGLE_PAGE page mode, then problem is not reproduced.

Hello,

the search results in a PDF generated with report is not correct. Again...

Please fix this bug and add this scenario to your tests.

Steps: Search for a text in a pdf.

Reproducible in 17.1.23.606 - SRD .NET6

Steps to reproduce the behavior:

1. Open Product Sales report
2. Click on textBox3
3. Select "Split cells" from the context menu.
4. Click "Undo"

Expected behavior
No exceptions
Actual behavior
Table Body has 9 rows but 3 are expected.

Screenshots
Screenshot

Hi Team,

I would like to request an HTML5 ASP.NET Core Report Viewer similar to the MVC version with wrappers.  It would be great to be able to utilize Razor Syntax for developing instead of pure jQuery.

Thank you!

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.

When the reporting service fails to generate a report document, the Get Document Info request returns a 500 response with the error message thrown from within the reporting engine. However, instead of displaying the error message in the viewport, the Native Blazor Report Viewer displays a message falsely suggesting that the report is still being rendered when the rendering has, in fact, failed.

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

We have successfully downloaded and installed Google Open Sans fonts (from the URL:  https://fonts.google.com/specimen/Open%20Sans#:~:text=Open%20Sans%20is%20a%20humanist%20sans%20serif) to a Linux Ubuntu-based Docker container using the following Dockerfile script to install the dependencies and the fonts:

RUN apt-get update && apt-get install -y libfreetype6 libfontconfig1 fontconfig unzip

#Google Fonts
RUN mkdir -p /usr/share/fonts/truetype/googlefonts && cd /usr/share/fonts/truetype/googlefonts
COPY ["Open_Sans.zip", "/usr/share/fonts/truetype/googlefonts"]
RUN unzip -d /usr/share/fonts/truetype/googlefonts /usr/share/fonts/truetype/googlefonts/Open_Sans.zip
RUN rm -f Open_Sans.zip
RUN ls -al /usr/share/fonts/truetype/googlefonts
RUN fc-cache -fv
RUN fc-match OpenSans

Open_Sans.zip file should be in the solution folder when running the Docker from Visual Studio.

The fonts are displayed as expected when previewing in the browser. When exporting to PDF though, the Reporting engine throws the following exception when Open Sans font is used:

CSharp.Net8.Html5IntegrationDemo Error: 0 : System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Telerik.Reporting.Pdf.Fonts.TrueType.TrueTypeCollectionHeader.Read(FontReader fontReader)
   at Telerik.Reporting.Pdf.Fonts.TrueType.TrueTypeCollectionHeaderVersion2.Read(FontReader fontReader)
   at Telerik.Reporting.Pdf.Fonts.TrueType.FontCollectionProgram.Decompile()
   at Telerik.Reporting.Pdf.Fonts.TrueType.FontCollectionProgram.EnsureFonts()
   at Telerik.Reporting.Pdf.Fonts.TrueType.FontCollectionProgram.get_Fonts()
   at Telerik.Reporting.Pdf.Fonts.TrueType.FontCollectionProgram.SelectFontProgram(String fontName, String fontFamily, Boolean bold, Boolean italic, Boolean underline, Boolean strikeout)
   at Telerik.Reporting.Pdf.Fonts.TrueType.TrueTypeDescriptor..ctor(IFont engineFont)
   at Telerik.Reporting.Pdf.Fonts.TrueType.TrueTypeDescriptor..ctor(PdfFont font)
   at Telerik.Reporting.Pdf.PdfFontTable.GetDescriptor(PdfFont font)
   at Telerik.Reporting.Pdf.PdfFontDictionary..ctor(PdfDocument document, PdfFont drawingFont)
   at Telerik.Reporting.Pdf.PdfFontType0Dictionary..ctor(PdfDocument document, PdfFont font)
   at Telerik.Reporting.Pdf.PdfFontTable.GetFont(PdfFont font)
   at Telerik.Reporting.Pdf.PdfPageDictionary.GetFontName(PdfFont font, PdfFontDictionary& fontDictionary)
   at Telerik.Reporting.Pdf.Rendering.PdfRenderer.GetFontName(PdfFont font, PdfFontDictionary& fontDictionary)
   at Telerik.Reporting.Pdf.Rendering.PdfRendererGraphicsState.Update(PdfFont font, IBrush brush, Int32 renderMode)
   at Telerik.Reporting.Pdf.Rendering.PdfRenderer.Update(PdfFont pdfFont, IBrush brush, Int32 renderMode)
   at Telerik.Reporting.Pdf.Rendering.PdfRenderer.DrawString(String text, PdfFont pdfFont, IBrush brush, RectangleF rect, Boolean rightToLeft)
   at Telerik.Reporting.Pdf.Drawing.PdfGraphics.DrawString(String s, IFont font, IBrush brush, RectangleF rect, StringFormatBase format)
   at Telerik.Reporting.ImageRendering.CanvasPdf.DrawRegularChunk(String text, StringChunkContext context)
   at Telerik.Reporting.ImageRendering.CanvasBase.DrawStringChunk(String s, 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.ProcessingElementWriter`1.Write(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.WriteStartOperationsDispatcher.Write(IElementWriter writer, LayoutElement element, ElementPageInfo pageInfo, DocumentWriter documentWriter)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.Write(IElementWriter writer, LayoutElement element)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(TextBox textBox)
   at Telerik.Reporting.Processing.TextBox.Accept(ProcessingElementVisitor visitor)
   at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
   at Telerik.Reporting.Writing.WriteOperationsDispatcher.DispatchWriteOperation(LayoutElement element, ElementPageInfo pageInfo)
   at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
   at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.StartElement(LayoutElement element, ElementPageInfo info)
   at Telerik.Reporting.Paging.PageStartElement.OutputToPage(IPageHandler handler)
   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()
CSharp.Net8.Html5IntegrationDemo Error: 0 : An error has occurred while rendering the report: System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.SpinThenBlockingWait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.InternalWaitCore(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(CancellationToken cancellationToken)
   at Telerik.Reporting.Paging.PageCompositionBase.SeparateThreadOutputBehavior.Finish()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)

The same report with the same fonts is rendered successfully on Windows with the Standalone Report Designer for .NET 8 with both GDI and Skia graphics engines.

Watermark Images with higher than the report rendering DPI are displayed clipped in PPTX rendering.

In PDF, preview of the designers and DOCX the same watermark is shown as expected.

If the DPI of the image is 96 as the default Windows machine DPI used for rendering, the Watermark is displayed correctly also in PPTX.

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