Hi Team,

Currently, the Angular Report View doesn't appear to support the Ivy rendering. As of Angular 16 (released 4 days ago), the legacy rendering mode is fully removed. Which means the ReportViewer will no longer work in ng16 or later.

So this feature request is to move the ReportViewer to support Ivy (which will support Angular v9 to v16 and later).

Thank you,

Maks

I apply the operator TOP N (=5) to get only the first 5 records of a dataset sorted by a DateTime field. It sorts the data correctly as seen in the previewed report, but still returns all data records rather than the first 5 of them.

If I apply the TOP % operator, the dataset seems filtered as expected.

The workaround I have found is to apply second TOP N filtering with an empty expression as seen in the linked screenshot.

I have attached also a sample report demonstrating the issue and the workaround.

When exporting a graph that has multiple line series and a category scale to CSV, the error "object reference not set to an instance of an object" is thrown.

More specifically, the issue occurs when one or more of the series do not have a corresponding non-null value for every category.

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.

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.

Currently the behavior of the Web Designer and Standalone Designer is different in regard to DateTime Report Parameters and its "Kind" property.
The Web Designer will assume the value is of Kind "Utc" and the Standalone Designer uses "Unspecified".

This recently became more of an issue since the newer PostgreSQL Provider versions are a lot more strict regarding the "Kind" property:
Npgsql: Timestamp rationalization and improvements

The consequence of this is not being able to use Sql parameters which will work in both the WebDesigner/WebViewer and the StandaloneDesigner:

To resolve this issue right now, one would need to resort to ugly workarounds:

• Add a custom function which receives a DateTime "d" and DateTimeKind "k" value and returns the DateTime value "d" with the Kind set to "k"
  • Having to include a user dll to add that function seems overkill
  • You will need to change every report currently in use
• Change the behavior of the WebDesigner to match the behavior of the Standalone Designer by using a custom IReportSourceResolver, manipulating currentParameterValues 
  • The Kind Property is set to "Unspecified" which is arguably the worst option to take between the three

To properly address this issue it needs to be possible to set the Kind property in the Viewer. Or at least the behavior between the WebDesigner and Standalone Designer should be the same.

Additionally/Alternativly it should be possible to set the target Kind in the Report Parameter.

With kind regards,
Dominik Rothert

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

Report is working fine in local IIS but not in IIS server. See error details below.

Error creating report instance (Report = 'AttendanceTagging.trdp').
An error has occurred.
A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.

Currently the generated accessible PDF documents contain tagged elements, but lack information about the logical structure of the PDF document. This prevents screen readers of correctly reading the PDF document contents. The tools like PAC (PDF Accessibility Checker) do not display correctly the document structure.

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.

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.