Here is a snippet from the file '/@progress/telerik-angular-report-viewer/dist/es/telerik-report-viewer.component.js' in Telerik Reporting NPM repository of the Angular Viewer that hard-codes the message:

TelerikReportViewerComponent.decorators = [
        { type: Component, args: [{
                    selector: 'tr-viewer',
                    template: '<div [ngStyle]="containerStyle" [attr.id]="reportViewerID" #container>Loading Report Viewer...</div>',
                    styleUrls: [],
                    encapsulation: ViewEncapsulation.None,
                },] },
    ];

Currently, there is no easy way for localizing or removing this message in an Angular-wise approach.

Utilizing Native Blazor Report Viewer with Telerik Blazor UI 4.0 results in some toolbar icons appearing blank. The icons are still functional.

Switching to Blazor UI 3.7 fixes the issue.

When HTML entities are used in an embedded expression of the HtmlTextBox, they are parsed.

The same does not happen when the "= ..." expression syntax is used.

For example:

This expression works.

= Replace(Fields.Column2, 'less than','<')

This one throws an error.

{Replace(Fields.Column2, 'less than','<')}

When selecting an item in the report designer (for instance a textbox) if i go in the properties and i set the anchoring property, i have to click in an other property to get my anchor property to be updated.

I have attached a video that reproduce the problem :

Select a textbox, go to anchoring in the property explorer

Set the anchoring

And click in the report itself

As you can see anchoring property hasn't been updated.

Hello,

in the WebReportDesigner it is currently only possible to add a TypeSelector to a StyleRule. (see screenShot: "WRD_StyleRule_Add_Selector.png").

Interestingly, when a report already contains a StyleSelector, it is possible to edit and save the changes, this is great :-), (see screenShot: "WRD_StyleRule_Edit_StyleSelector.png").

Would be great if we could add a StyleSelector ;-).

Best regards

Alexander Schneider

In the Explorer tab of the Web Report Designer, when trying to open the context menu of a table(crosstab)'s column(row) group, nothing happens and an error is logged in the browser console.

Steps to reproduce:

1. Navigate to a table(crosstab)'s column/row group in the Explorer tab.
2. Try to open the context menu with the ellipsis button (...).

The current implementation of the angular / HTML5 report viewer requires a script-src 'unsafe-eval' in a content-security-policy.
This is quite unfortunate in terms of security considerations. Please remove this requirement.

Kind regards
Claudio

I have a Graph with a Legend with Position LeftCenter. I want the text of the legend to be Right-aligned.

However, neither the Series > LegendItem > Style > TextAlign gets respected, nor the GraphLegend > Style > TextAlign. the text is always left-aligned.

The value '姓名：' is rendered on two lines in a TextBox under Linux. The colon symbol at the end '：' appears on the second line no matter how wide is the TextBox. The colon character itself is a special Unicode Character “：” (U+FF1A).

There are other symbols that may be used instead of the colon to reproduce the issue in Linux rendering. Under Windows, the text is rendered as expected.

The R2 2023 Standalone Report Designer for .NET cannot be run with the .NET 7 runtime that previously worked(approach - https://docs.telerik.com/reporting/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net).

Error: 'Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.'

Setting values to the request body in the WebServiceDataSource component via inline parameters turns the values of the string regardless of what is passed in the design/runtime parameter expression.

For example, in the following image, I set the runtime expression to be =2000 which should embed that value as a number to my request's body on previewing the report. Instead, the value is sent as the string "2000":

When I have a report that uses the Shape Report Item and I export it to Excel(XLSX) in Linux, upon opening the Excel file, I am met with the following warning:

We found a problem with some content in "Report.xlsx". Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes

If I do not have any report opened in the Web Report Designer, and then open the Asset Manager, I am not able to close the Asset Manager afterward.

Instead, when I click on the 'X' button to close the Asset Manager screen, I get the following error:

Uncaught TypeError: this.designSurfaceManager.ActiveDesignSurface is null
    updatePreviewButtonState http://localhost:51864/api/reportdesigner/designerresources/js/webReportDesigner-17.1.23.718.min.js/:9
    restoreMainMenu http://localhost:51864/api/reportdesigner/designerresources/js/webReportDesigner-17.1.23.718.min.js/:9
    createAssetManagerOverlay http://localhost:51864/api/reportdesigner/designerresources/js/webReportDesigner-17.1.23.718.min.js/:9

The 'Workspace Preferences' view also cannot be loaded in this scenario(no report).

Adding a custom font as PrivateFont in the appssettings.json is not respected.
When the font is installed, it works also for the report in the viewer.

The issue may be reproduced with the Reporting WinUI example for .NET 6.

The Stack Trace states:
CSharp.Net6.WinUIIntegrationDemo Warning: 0 : A font family for font "MICR" cannot be found. Exception: Font 'MICR' cannot be found. Font 'MICR' is substituted with font 'Microsoft Sans Serif'.

Currently, if a ReportBook contains nested ReportBooks that have their own TOC sections, the final document generated from the main ReportBook will not contain any TOC sections.

Adding the ability to display the TOCs of nested ReportBooks will be useful in preserving the original design of each ReportBook. 

When a system tells users they should look into the report parameters as the reason the report isn't displaying.  It's reasonable for your users to believe you aren't misleading them. 

The report viewer error message misleads users.  In reality the parameters are correctly configured and it the repot URL could be wrong.  Or a variety of other issues are at play; for instance, a problem with you connection string will also return the "Unable to get report parameters" error message.  I'd like to see this error message at minimum changed to "report can't display."   It's better to throw out a generic message vs having users spend hours or days troubleshooting the report parameters.  Better yet a proper catch/validation system put into place please.