My project uses the following two dependencies:
However, when I build my application and navigate to the page of the Native Blazor report viewer, the following error is thrown:
“Telerik.Blazor.Components.TelerikWindow does not have a property matching the name ‘Centered’.” at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.ThrowForUnknownIncomingParameterName(Type targetType, String parameterName) at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.SetProperties(ParameterView& parameters, Object target) at Microsoft.AspNetCore.Components.ParameterView.SetParameterProperties(Object target) at Microsoft.AspNetCore.Components.ComponentBase.SetParametersAsync(ParameterView parameters) at Telerik.Blazor.Components.TelerikWindow.SetParametersAsync(ParameterView parameters) at Microsoft.AspNetCore.Components.Rendering.ComponentState.SupplyCombinedParameters(ParameterView directAndCascadingParameters)
We see a console error when navigating away from the Blazor Native report viewer page. The page that contains the breadcrumb and the viewer has query-supplied parameters.
Using the text-indent CSS setting results in part of the text on the first line being cut off:
I am using the obsolete `Telerik.Reporting.Chart` type for a chart in a report. When I attempt to preview the report, an error is thrown:
The type "Telerik.Reporting.Chart" contained in assembly "Telerik.Reporting, Version=19.2.25.1001, Culture=neutral, PublicKeyToken=a9d7983dfcc261be" cannot be loaded.
To help improve the application's security, the reporting engine prevents loading types that are not essentially needed or listed as trusted by the user. If you consider particular types or assemblies as trusted include them in the corresponding TypeReferences or AssemblyReferences element of the 'Telerik.Reporting' configuration section in the application's configuration file.
When using the Native Blazor report viewer with the latest version of Telerik UI for Blazor (12.0.0), the following exception is thrown:
Unhandled exception rendering component: Object of type 'Telerik.Blazor.Components.TelerikToolBar' does not have a property matching the name 'Adaptive'.
I am using the new Coded Reports feature in the Standalone Report Designer for .NET, and I have a class library with reports, that depends on another project.
When I try to load a report from the reports class library, I get an error that the dependent project's assembly cannot be loaded despite being present in the report folder's bin directory.
In MSSQL, you may use syntax like 'StoredProcedureName;1' to indicate stored procedure versioning, but it is not yet supported by Telerik Reporting.
I use such syntax and need to remove the version to make this work in Telerik Reporting.
It would be great if you also added support for versioning in MSSQL stored procedures.
If you add transparency to a Graph line, for example, the Y-axis, with an alpha value: '150, 255, 255, 192', it is respected in the Standalone Report Designer, where the rendering format is Image.
In the Web Report Designer and in the HTML5 Report Viewer preview, the alpha value is ignored, and the color is rendered as '255, 255, 192', which removes the transparency.
Currently, if the SkipBlankPages property is set to True and there is not any significant content in the report, the following message will be displayed in the designer and the viewer: The current data set presented in the report did not produce any significant content, so no pages were generated. If you need to see the whole report content, including blank pages, please contact the report author.
When the current thread culture is set to Turkish (tr-TR), the lowercase and uppercase conversion rules differ from English — especially for the letter "i".
In Turkish:
"i".ToUpper() → İ (with a dot)
"I".ToLower() → ı (dotless i)
Our assumption that the Telerik HtmlTextBox internally parses and maps HTML tags by converting them to uppercase. When the Turkish culture is active, this conversion causes tag names to break, which is not a valid tag, so ordered lists fail to render.
Best regards,
Denis