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:
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 > 0, Fields.NutzungMaschinenbreite, "")" 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.
Almost any object can be set to grow (CanGrow = True). Which makes the object grow if the text is too long.
I believe you need a function for making the text fit inside the object.
“ShrinkToFit = True”
This would shrink the text so that it fits inside the object. So if the font size is 20 and a long text wouldn’t fit inside the object, the font size would shrink until it fits.
Today we need to set several conditional formatting rules for this and it’s far from perfect.
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.
Greetings,
I have a situation, I need the telerik reporter filters to be more intelligent, that is to say that they are nested and that the information they present when loading the data is according to the information selected from the other filters.
Example :
REPORT VEHICLE SPECIFICATIONS
selected > Filter : Person Name
Cars : List of Cars of a Person
Expected Results : List of Cars of selected person
Actual Telerik Report Results : List of Cars of ANY person
How do i work with nested filters ?
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 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