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.

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!

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

In Telerik Reporting versions before 18.1.24.514, I could change the order of items in a section by dragging an item up or down in the Report Explorer list.

If I try that now, nothing seems to happen on the screen. Dragging does not appear to change the position of an item in Report Explorer; the item appears to be fixed in place.  However, if I close the report and reopen it, the position of the item may have changed.

The same happens if I use Send To Back/Brink to Front on an item.  The new item position is not updated in the Report Explorer. 

Password-protected PDF documents generated with Telerik Reporting have blank pages when opened with an iPhone.

After updating the Reporting version to v18, some error messages display the <br /> HTML element as text in the HTML5 Report Viewer.  The issue was not present in v17.

I have created an abstract class in my report library that inherits from Telerik.Reporting.Report. When I try to load the project's assembly in the Standalone Report Designer to import those reports as TRDP, an exception is thrown while the application tries to load the assembly that there are report types that do not have a parameterless constructor.

To resolve the issue, I had to remove the 'abstract' modifier. However, that should not be necessary. The wizard should ignore abstract classes or at the very least, let me import the other report types while displaying a message that there are report types with parameterless constructors.

When trying to open reports from an assembly in the Standalone Report Designer so that they can be imported, if there are types that inherit from Telerik.Reporting.Report that do not have a parameterless constructor, this will cause an exception as it is required for the report types to have such a constructor, otherwise, the wizard cannot import them into TRDP.

In this scenario, the report types that do not have a parameterless constructor should be written to the trace or in the exception message dialog so that the user can see which are the problematic types and correct them.

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.