In Blazor Web Assembly you cannot host the Reporting REST Services due to technical restrictions related to the System.Drawing assemblies (GDI).

It would be very useful to have a Visual Studio project template creating only the Web Designer's Service in a separate project, so that we may use it in a web designer hosted in Blazor WASM.

Nested OLs do not start with the number of their parent but instead, start counting completely anew.

Offer a solution allowing nested OLs to generate this form of rendering.

1.   title1

1.1   subtile11

1.2   subtile12

2.   title2

2.1   subtile21

2.2   subtile22

2.2.1   subtile221

2.2.2   subtile222

2.3   subtile23

3.   title3

Currently, the fields' names are case-sensitive for those 2 data sources while other data sources, like the CSV for example, will ignore the casing.

For example, if there is a JsonDataSource with a Column1 field, it has to be written exactly as is in the expression while in the CsvDataSource, the field will be resolved even when written like Fields.column1 in an expression.

Currently, the WinUI ReportViewer has a hard dependency on Windows due to the fact that the internals rely on the Win32 print dialog.

This means I cannot define the ReportViewer in a WinUI class library to be shared with multiple front-end WinUI projects. If you attempt to do this, there's an internal crash because the project cannot resolve  System.Windows.Forms.

This feature request is ask if you can replace the Win32 print dialog with the WinRT printing API. 

Research Note:  Here's a GitHub thread where Microsoft is discussing the topic Question: Printing in WinUI 3 Desktop · Issue #4419 · microsoft/microsoft-ui-xaml (github.com). Here's their current recommendation:

var hWnd = WinRT.Interop.WindowNative.GetWindowHandle(App.StartupWindow);
var printMan = PrintManagerInterop.GetForWindow(hWnd);

await PrintManagerInterop.ShowPrintUIForWindowAsync(hWnd)

The chart BarSeries has DataPointStyle > LineColor set to white so that there is a white small gap between them. However, this has led to incorrect behavior if the chart contains small values, in relation to other values. The chart shows lines that should not be there:

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

When the "Kind" localization property of the Web Report Designer is changed, the ExternalStyleSheets editor breaks, and it cannot be used.

Hardcoded values are used when checking against "LocalizedName" in a few other places as well. Some of which are:

• "Kind" === e.LocalizedName

• "Path" === e.LocalizedName

• "Path" !== e.LocalizedName

• "Width" === this.LocalizedName

• "Height" === this.LocalizedName

P.S. It seems more logical to me to implement text wrapping using spaces rather than spaces + tags used, as it is now. But the support team have assured me that this is not possible.

When developing a Telerik report template with the intention of exporting to Excel, I observed the % sign was not displaying for positive numbers in the exported Excel file. The format we were using was {0:N2}%. The results displayed on the HTML report viewer and the Word export document was correct:

However in the excel file result, the cells were formatted without the % for positive numbers, and with the % for negative numbers.

Upon further inspection, I noticed the excel cell formatting was translated as:

This format would not generate the % symbol for a positive number as the trailing % is missing before the semi-colon.

We are fixing this by using the below Format specification directly in the Report Designer:

{0:#,##0.00"%";-#,##0.00"%"}

which is directly retained in the excel custom format:

While I understand that N, C etc. C# number formats are supported according to the design considerations and this bug is also technically resolved by using UseExtendedFormatting (setting this to false translates {0:N2} to #,##0.00"%"), this seems like an unexpected result of translating the format codes that does not match the standard behavior of {0:N2}%. Reporting this behavior for review.

If you set the anchor property and validate it, if I come back on the property, the designer does not show the current anchor.

As you can see, anchoring is defined to left, but it is not shown in the dropdown of the property. The anchoring left should be grey.

When a report has a report parameter using a data source, that is visible and has AllowNull set to True, if the value initial value is invalid, no report parameter widget is loaded at all for this parameter.

If this is the only report parameter, the parameters area is not rendered at all, even though the toolbar indicates that it is active.

The issue can be reproduced by loading the attached report in the native Blazor Report Viewer.

Reports.zip

I have designed a report that includes an embedded SubReport. When I render it to PDF, it looks correct.  When I render it to CSV, there are two issues that are probably related:

1. The heading row columns should contain the main report's detail row textbox names followed by the SubReport 's detail row textbox names.  However, the SubReport 's detail textbox names are repeated a few times instead of just included once.
2. In the situation where there is no detail row in the SubReport, a CRLF is missing at the end of the main report's detail data.  The next main report detail data appears on the same row, following the previous main report's last detail column -- it should begin on the next line.

I understand that CSV Rendering is not recommend for hierarchical output as described in the CSV Design Considerations. However, I am using the Hide the SubReport if no Values to not display the SubReport when there is not data. The hidden SubReport implementation can be seen in the below binding expression.

<Bindings>
    <Binding Expression="=Count(Fields.AP_OPN_CHK_VCH_NO_C)>0" Path="Parent.Parent.Parent.Visible"/>
</Bindings>

Using the above approach, the master report is missing a CRLF when the detail data is not visible. The record shows it appended to the previous record.

I started working with Support on this issue and have discovered that it might be a bug. As a result, I am also attaching their sample to help replicate the issue. For the pdf and csv output see the first attachment in the original ticket.

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','<')}

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.

I have encountered scenarios where I want to return different results based on fields value or some expression. While I can use nested ternary operations this is not ideal as it can be difficult to read and maintain, particular for newer report designers. It would be helpful to have SWITCH and IFS statements modeled after those provided by Excel.

SWITCH would be helpful for cases where I want to check against a few different literal values and return different results.

IFS would be helpful for cases where I want to evaluate different expressions and return different results.

Modeling these after those in Excel would be sufficient, though, for more advanced cases being able to write C# code inline with the report would be helpful (will submit as a separate request).

In this file t.folder is lowercase which should be Capital t.Folder

t.folder  throws error

 t.Folder return value

same or files vs Files