Using a Toggle Visibility action to expand/collapse recursive SubReport results in the "Node should be found among parent nodes" error. The recursive SubReport renders fine without the action.

The report from the How to represent hierarchical flat data in report recursively - Telerik Reporting KB article was used as a base.

Recursive sub-report with hierarchical data. When expanding/collapsing, all nodes get expanded or collapsed.

I would expect only the selected node to be expanded/collapsed.

For reference, the report from the How to represent hierarchical nested data in report recursively - Telerik Reporting KB article was used as a base 

The JS file with the stringResources shipped with the installation at the following location:

C:\Program Files (x86)\Progress\Telerik Reporting <Release>\Html5\ReportViewer\js

is incorrect, it should be as shown in the Localization - Telerik Reporting article.

Basically, line 9 should be changed to:

; (function (trv, $) {

while lines 178 to 180 should be like this:

    trv.sr = $.extend(trv.sr, sr);

}(window.telerikReportViewer = window.telerikReportViewer || {}, jQuery));

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.

The attached 'Test.svg' image markup file contains 'use' statements that lead to duplicating part of the image parts when rendering the report in PDF.

The other file in the archive, 'Test-noUsings.svg' is the same image without 'use' statements and doesn't have this problem.

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

According to the Excel Rendering Design Considerations article:

• The "f" DateTime format string should result in a full date/time pattern with a short time pattern.
• The "F" DateTime format string should result in a full date/time pattern with a long time pattern.

After exporting to XLS/XLSX, the time formats are as follows:

• "f" -> full date/time pattern with a long time pattern.
• "F" -> full date/time pattern with a short time pattern.

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:

The version is encoded twice in each QR code; once at the top right and once mirrored at the bottom left. A comparison of the boxes tells which is the version.

The Reporting tool doesn't mirror the version correctly at the bottom left, and some strict barcode readers don't recognize the barcode correctly.

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.

The old report that I have has the following table cell definition:

<TableCell RowIndex="2" ColumnIndex="0" RowSpan="1" ColumnSpan="1">
  <ReportItem>
    <TextBox Width="7.471cm" Height="0cm" Left="0cm" Top="0cm" Value="= Iif(Fields.NutzungMaschinenbreite &gt; 0, Fields.NutzungMaschinenbreite, &quot;&quot;)" Name="Z2S3NutzungMaschinenbreite" StyleName="">
      <Style TextAlign="Center" VerticalAlign="Middle">
        <BorderStyle Default="Solid" />
        <BorderWidth Default="2px" />
      </Style>
      <ConditionalFormatting>
        <FormattingRule>
          <Style BackgroundColor="LightGray" />
          <Filters>
            <Filter Expression="Fields.Eigene" Operator="Equal" Value="= True" />
          </Filters>
        </FormattingRule>
      </ConditionalFormatting>
      <Bindings>
        <Binding Path="Height" Expression="= Iif(First(Fields.Typ) = 'H', '0,66cm', '0,003cm')" />
        <Binding Path="Visible" Expression="= Iif(First(Fields.Typ) = 'H', 'True', 'False')" />
      </Bindings>
    </TextBox>
  </ReportItem>
</TableCell>

Since the Height of the inner TextBox is '0cm' the corresponding processing cell becomes Null when processing the Table and the Reporting code throws a NullReferenceException:

[NullReferenceException: Object reference not set to an instance of an object.]
   Telerik.Reporting.Processing.Table.ForEachCell(Action`1 action) +121
   Telerik.Reporting.Processing.Table.MeasureDataItemContent(IMeasureContext context, SizeLU availableClientSize) +622
   Telerik.Reporting.Processing.DataItem.MeasureContent(IMeasureContext context, SizeLU availableClientSize) +86
...

The error message may be made more informative, stating that the table row should be at least '10px', as the designer warns in design time.

When Kendo version 2023.1.314 is used, the tooltips of the HTML5 Report Viewer and its wrappers flicker when the cursor hovers above them.

Telerik Reporting Version: 17.0.23.315

Currently, the ReportDesignerControllerBase class does not enforce its own JsonSerializerSettings, rather it uses the ones set globally, on the application level. This could potentially lead to errors since the Web Report Designer requires the data to be serialized in camelCase. When PascalCase is used, certain functionalities get broken.

A way to avoid this would be to explicitly define JsonSerializerSetting in the ReportDesignerControllerBase class so that the Report Designer service does not break regardless of the setting defined on the application level.