When certain fonts are used, the text of reports exported to PDF looks different between the Skia and GDI rendering engines, even if the fonts are fully embedded.

For example, if the TT Norms font is used and the report is exported to PDF (full font embedding) with both engines, the document rendered by Skia is much larger and looks different than the GDI-rendered document.

The Export dropdown menu looks like the following image when using Kendo UI 2023.2.606+

When generating PDF/UA files, we need to have special objects that are read by an internal system but ignored by screen readers. This cannot be achieved with the existing functionality.

It would be beneficial if we could configure reports so that specific objects inside the generated document are ignored by screen readers. For example, by setting a special value to the AccessibleRole property of a text box. 

If the file `WebReportDesignerSettings.json` doesn't exist before running the Web Designer REST Service, the latter will create it. However, the file will remain locked and the service will throw the exception:

"The process cannot access the file '/app/Telerik_Reporting/WebReportDesignerSettings.json' because it is being used by another process."

When the file exists, the problem will be avoided, which leads to the workaround - create the file at a starting point of the application. Here is a sample code:

static void InitFile()
{
            var path = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), "Telerik Reporting", "WebReportDesignerSettings.json");
            File.Create(path).Close();
}

To allow localization for the WebReportViewer in Version 17.1.23.718 and before, it was enough to provide a customized Version of "telerikReportViewer.stringResources.js", which extended the property "window.telerikReportViewer.sr".

This worked for both, the WebReportViewer and the Preview of the WebReportDesigner. With version R3 2023 SP1 (17.2.23.1114), this approach does not work anymore.

When an item has borders applied and the report is exported to PDF, the border lines "stick out" at the joints. The image below illustrates this.

Some additional information about the issue:

• The issue was first introduced in the R1 2017 SP2 Release.

• The issue seems to appear only in Chromium-based browsers.
  • Microsoft Edge -> reproducible
  • Google Chrome -> reproducible
  • Opera -> reproducible
  • Mozilla Firefox -> not reproducible
  • Adobe Acrobat -> not reproducible

• The borders "stick out" differently based on the zoom level. In some zoom levels, there are no issues, in others the borders "stick out" at the bottom, right, etc. 

When rendering a Report in PDF with Skia Sharp, the Arial Bold Italic font is rendered as Normal. Arial Bold and Arial Italic fonts are rendered correctly.

When rendering with GDI+ all fonts are displayed correctly.

Currently, I can send only String content when making a POST request with the WebServiceDataSource component.

My Web API requires me to the content as Form URL Encoded and I cannot do that with the WebServiceDataSource component, and have to use the ObjectDataSource component to manually request the data correctly.

If a WebServiceDataSource has inline JSON data for design-time preview, this inline data is not used when the report is designed with the Web Report Designer. Instead, the data is requested from the service both during design time and during live preview.

On the other hand, the Standalone Report Designer works as expected. I.e. inline data is used during design time and live data from the service is used during the preview.

A search feature in the report editor would be very useful - being able to find all report components/items with any property containing input search text. An added bonus would be having a filtered or highlighted view of the properties of result items, indicating matches.

Being able to find expressions and other properties where some name/value is being used is a very helpful benefit.

UI functionality like that of the search in the Solution Explorer of Visual Studio, with a filtered hierarchical tree structure result view could work well, otherwise a separate results list might be good too.

My PostgreSQL query contains an Integer parameter. In the Standalone Designer, it executes successfully both in design and in preview.

In the Web Designer, the same report is also previewed successfully. When I try to configure the SqlDataSource though, if I run the Execute Query in the final step, the database returns an error stating '...operator does not exist: integer = text...'

If the parameter is String, the query runs fine in design time of the Web Designer as well.

Dear Telerik 

Please see thread on Report does not bring byte[] image through to PictureBox when rendered programmatically. | View Ticket | Your Account (telerik.com)

KR

David

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 use HTML content like the below in an HtmlTextBox:

<a style="color: red" href="some link here">some text</a>

The color is not respected when I export to PPTX. The output color of the generated link is always the default blue. In the rest of the formats that support hyperlinks, the color is correct.

I tried to wrap the <a> tag also with <p> and <span> with the same color setting, to no avail.

When the input data of a pie chart is such that some of the series are insignificant enough not to be drawn on the surface area, a DocumentRenderException with the message "The operation was canceled" is thrown by the Reporting engine.

Enlarging the pie chart or hiding/removing its data point labels clears the error.