We use Telerik's report books extensively - and find that to be a very powerful way to create dynamically generated reports. The feature request is: if a report's datasource doesn't fetch any rows don't add a blank page to the report book.
I use the Verdana font in my report titles. In the desktop designer and PDF documents, the text appears as expected.
In HTML5 and Blazor Report Viewers, though, the characters like 'p', 'q ', and 'y' appear cut off:
It would be good a maintain the scroll position on the parent page while navigating back from a drill-through report (using the back button of the report viewer) specially if the parent page contains a vertical scrollbar. This would enhance the user experience and eliminate the need to scroll back to the original position.
The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.
The workaround is to avoid using the SQL DataSource wizard and edit the data source properties directly in the properties grid. You can check the attached silent video that demonstrates how to do so.When a Table has a Group PageBreak that splits the Table into more than one page, the items below the table are rendered after the first part of the Table (after the first page break), rather than under the whole table.
The issue occurs in hard pagination: PrintPreview of the viewers, PDF, etc.
After upgrading Telerik.ReportViewer.BlazorNative to version 20.2.26.1007, rebuilding a project targeting .NET 9 or later fails with the following error:
Severity Code Description Project File Line Suppression State
Error (active) The asset 'C:\...\BlazorApp1\Debug\net10.0\compressed\14jp1i84hx-{0}-2x8nbomfaf-2x8nbomfaf.gz' can not be found at any of the searched locations 'C:\Users\<user>\.nuget\packages\telerik.reportviewer.blazornative\20.2.26.1007\staticwebassets\css\reporting-blazor-viewer.css.map' and 'C:\Users\<user>\.nuget\packages\telerik.reportviewer.blazornative\20.2.26.1007\staticwebassets\css\reporting-blazor-viewer.css.map'. BlazorApp1 C:\Program Files\dotnet\sdk\10.0.301\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets 276
-----------------------------------------------------------------------------------
The issue occurs because the NuGet package declares a CSS source map as a static web asset but does not include the corresponding file.
For the available workarounds, refer to the following Knowledge Base article: Missing CSS source map causes build failure in .NET 9 and later with Telerik.ReportViewer.BlazorNative 20.2.26.1007
The data source preview in the web report designer does not show the full shape of the query. It has no horizontal scroll bar to verify the preview data for the entire projection.
Please consider addressing this.
I use Zoom in my report definitions, which I edit with the Standalone Report Designers. The TRDP and TRDX reports work fine with Zoom. However, if I save a report with a non-default Zoom (e.g., 4.0) to the new TRDJ format, then I cannot open this report in the designer.
Here is the exception when trying to open the TRDJ report:
System.ArgumentException: Object of type 'System.Double' cannot be converted to type 'System.Single'.
at System.ComponentModel.ReflectPropertyDescriptor.SetValue(Object component, Object value)
at Telerik.Reporting.Serialization.ObjectReader.ReadValue(Object obj, PropertyDescriptor prop)
at Telerik.Reporting.Serialization.ObjectReader.ReadAttributes(Object obj, PropertyDescriptorCollection props)
at Telerik.Reporting.Serialization.ObjectReader.ReadProperties(Object obj)
at Telerik.Reporting.Serialization.ObjectReader.ReadObject(Type type)
at Telerik.Reporting.Serialization.ObjectReader.ReadXmlElement(String name)
at Telerik.Reporting.JsonSerialization.JsonSerializer.Deserialize(String value, IResourceHandler resourceHandler)
at Telerik.ReportDesigner.Packages.ReportDesigner.Serialization.JsonDocDataHandler.<>c__DisplayClass8_0.<DeserializeReport>b__0()
at Telerik.Reporting.Interfaces.IAnalyticsExtensions.UseFeature[T](IAnalytics analytics, Func`1 func, String featureName, String featureCategory, Field[] extraParams)
at Telerik.ReportDesigner.Packages.ReportDesigner.Serialization.JsonDocDataHandler.DeserializeReport(IDesignerLoaderHost targetHost)
at Telerik.ReportDesigner.Packages.ReportDesigner.Serialization.ReportDocumentDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
We render reports to PDF with ReportProcessor.RenderReport, and several renders run in parallel in the same process (background jobs). Occasionally the report items show this error inside the generated PDF instead of their values: "An error has occurred while processing TextBox 'textBox8': Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct."
Exception and stack trace:I use the Verdana font in CheckBox items.
In HTML5 and Blazor Report Viewers, the characters like 'p', 'q ', and 'y' appear cut off, just like in this issue:
The workaround with top and bottom padding doesn't work for CheckBox, though.
At the moment it's only possible to have your reports in old-fashioned projects.
It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).
I have a CS report that contains a SubReport with InstanceReportSource. I have it in a .NET 10 Classlibrary project.
I tried to edit this report as a coded report in SRD.NET. However, when I saved the report, in the 'designer.cs' file, the value assigned to the ReportSource of the SubReport was set to 'userreport1' that is not instantiated and throws.
Currently, the desktop viewers don't allow adding custom headers to their requests to the service.
In HTML5-based web viewers, this is possible through the AjaxPrefilter event.
Images taken with a mobile device are sometimes displayed in PictureBox rotated by 90, 180 or 270 degrees. The reason is that whenever a photo is taken, the device saves its current accelerometer orientation into a corresponding Exif tag with the image metadata, so this info is then read and taken into account by our Report Designer.
In Telerik Reporting versions before 18.1.24.514, I could change the order of items in a section by dragging an item up or down in the Report Explorer list.
If I try that now, nothing seems to happen on the screen. Dragging does not appear to change the position of an item in Report Explorer; the item appears to be fixed in place. However, if I close the report and reopen it, the position of the item may have changed.
The same happens if I use Send To Back/Brink to Front on an item. The new item position is not updated in the Report Explorer.
Hello Team,
I will be great if the Telerik Reporting REST Service Core could support System.Text.Json serialization.
Best Regards,
The following screenshot demonstrates what the ToC looks like when rendered with Skia on Linux.
Below is the expected result. Rendered with GDI on Windows.
I have been forcing my webservice data source into a workable solution for making GraphQL requests. Right now in order for us to use GraphQL, we have to build out the request manually with a string such as the following:
{"query: "query GetSomeResult($input: Int!) {result {id name}}",
"variables": "{"input": @parameter}"
}While this is a normal way to hand craft a GraphQL request, the issue I have is that it shouldn't need to be that hard. Also I get no intellisense or suggestion in regards to the data returning. This means that when I try to bind data to a text box, I have to visually validate that the [=Fields....] is actually correct by looking at the GraphQL query and at the code base. I would love to see the ability to to just say have a set of standard api technologies we could implement from such as GraphQL queries, GRPc queries, or any other contract style request. I would expect that the data source logic would be smart enough to parse the query (at least for GQL) and be able to provide reccomendations.
Also a major issue we have had is in being able to pass that data source to subReports, or dealing with any nested objects such as a user.address.addressLine1 would not be able to be found if address is a nested values like the following
user: {
address: {
addressLine1
}
}