When importing a report with the Standalone Report Designer for .NET, if the report or its items use report events, they are not automatically imported into the TRDP file.

It is currently necessary to manually type the method names in the corresponding properties in the report designer.

I am using the HTML5-based report viewer while connecting to a Report Server. However, the responses from the Report Server have a status code of 409 with the following error message:

Thе endpoint "Resources" is currently not accessible.

If I set both the "EnableAccessibility" and "ViewerRenderToolTips" device info settings to true, the generated PDF document is corrupted.

When the report contains SVG images with Arc segments, the rendering with Skia may result in the following exception:

Telerik.ReportDesigner.Net Error: 0 : System.InvalidOperationException: Invalid image data.
 ---> Telerik.Drawing.Skia.Exceptions.SkiaNotSupportedException: Exception of type 'Telerik.Drawing.Skia.Exceptions.SkiaNotSupportedException' was thrown.
   at Telerik.Drawing.Skia.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle)
   at Telerik.Reporting.Svg.SvgRectangle.Path(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgVisualElement.Render(ISvgRenderer renderer, Boolean renderFilter)
   at Telerik.Reporting.Svg.SvgVisualElement.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgRectangle.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgElement.RenderChildren(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgElement.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgFragment.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgDocument.Draw(ISvgRenderer renderer, ISvgBoundable boundable)
   at Telerik.Reporting.Svg.SvgDocument.Draw(Int32 rasterWidth, Int32 rasterHeight)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateBitmapImage(RadSvgImage svg, Size targetSizePx)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.DrawImage(RadSvgImage svg, CreateImageContext context)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateImageCore(CreateImageContext context)
   at Telerik.Reporting.Processing.Imaging.ImageItemBase.CreateImage(CreateImageContext context)

Hi Support team,

On ServerSide, when using a CultureInfo, with a NumberSeperator different then '.', e.g. CultrerInfo("de-DE"), it is not possible to Save a report.

It seems it is internally converted to a string based value and gets the different seperator and than can not be casted/converted back to double.

Best regards

Alexander Schneider

System Development | Loy & Hutz Solutions GmbH

I have multiline text in a TextBox item that has its Style > TextAlign set to Center.

It is rendered as expected with the GDI+ graphics engine.

When I switch to the Skia graphics engine in the Standalone Designer .NET, though, some lines are not centered correctly in PDF rendering:

In Preview of the designer, with PNG and OpenXML export the text is shown as expected.

I am using the HTML5 Report Viewer and have a multi-page report. When the report is previewed with the default pageMode setting, where pages are continuously scrollen into, the found search results are correctly highlighted.

However, if I use pageMode="SINGLE_PAGE" in the HTML5 Report Viewer initialization code, and I navigate to page 2 or further, the found results are not highlighted.

Hi

Currently, when referencing an assembly from appsettings.json in telerikReporting:assemblyReferences  , the Object Data Source wizard in Telerik Web Reporting displays all namespaces from that assembly, even if only one class is marked with [DataObject]. This results in unnecessary namespace clutter and can confuse report designers, especially in large projects where only a single data object is intended for reporting. See screenshots below:

Please provide a way to control which namespaces and/or classes are visible in the Object Data Source wizard. Possible solutions could include:
•    Only displaying namespaces that contain [DataObject] classes (filtering namspaces with no elments to display)
•    Allowing explicit inclusion/exclusion of namespaces or classes via configuration (e.g., in appsettings.json).
•    Supporting an attribute (such as [Browsable(false)] or a new custom attribute) to hide specific classes or namespaces from the wizard UI.

Thank you for considering this improvement!

The data member list in "Choose a data member" (step 2) of the objectDataSource wizard in the Web Report Designer does not appear to be in alphabetical order as it is in the Standalone Report Designer.

When there are many data members it is hard to pick the one you want when not ordered alphabetically.

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

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.

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.