I have a table with a detailed group with PageBreak set to 'After' and a crosstab inside the table with a row group that also has PageBreak set to 'After'. The pagination is respected in the preview of the designer, however, when exported to XLSX, there is only one worksheet generated.

If I remove only the PageBreak of the detailed table group, there is no pagination and the generated worksheet is only one.

If I remove only the PageBreak of the crosstab row group, there is pagination and the generated worksheet is correct in number. However, the content is not split as expected among the sheets.

If I make the detail table group static and remove its PageBreak, the pagination and the worksheets of the Excel document are as expected.

I am trying to implement the ISharedDataSourceStorage interface and the SaveAsync method receives a parameter of type SaveResourceModel from which I cannot access the description that the user might have written in the UI.

The support team told me that the FileSharedDataSourceStorage class internally uses a SharedDataSourceDescriptionHelper class for accessing the description. 

Please make the helper class public so that we may also use it when implementing the ISharedDataSourceStorage interface.

Some special characters, such as "🍁", break reports that are rendered with the Skia graphics engine in a Linux environment.

When the Gdi graphics engine is used on Linux, the reports are generated successfully. However, the Gdi graphics engine cannot be used on Linux with projects that target .NET 7 and later.

I am using the Blazor Web Report Designer widget which when initialized, loads its theme based on the @progress/kendo-theme-default - npm (npmjs.com) theme and overrides the styles in my Blazor application. There is no way to disable the loading of the designer's theme and the application looks inconsistent as a result.

Telerik Reporting supports various Barcodes.

It will be very useful if it also supports out-of-the-box Radio Frequency Identification (RFID).

The blog RFID vs Barcode: Comparison, Advantages & Disadvantages elaborates on the difference between the Barcode and RFID and why the latter is preferred in some scenarios. 

If you have the latest Telerik.Reporting NuGet package (18.3.24.1112) installed simultaneously with the Telerik.Documents.Fixed NuGet package, indeed, the compile time error occurs:

The type 'Size' exists in both 'Telerik.Documents.Core, Version=2024.4.1106.20, Culture=neutral, PublicKeyToken=5803cfa389c90ce7' and 'Telerik.Reporting, Version=18.3.24.1112, Culture=neutral, PublicKeyToken=a9d7983dfcc261be'

This undesired behavior is not reproducible with the previous version of Telerik Reporting. This is caused due to the fact that Telerik.Documents.Primitives.Size is contained in both assemblies/packages.

Workaround: Resolving Compile Time Error with Telerik.Documents.Fixed and Telerik.Reporting after Upgrading to Q4 2024

The HTML5 Report Viewer uses inline templates which may require enabling the unsafe-eval CSP policy.

The viewer should migrate to using CSP templates as shown in Getting Started with Content Security Policy (CSP) Templates - Kendo UI Templates - Kendo UI for jQuery.

I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.

It would be very useful if we could copy/paste Report Parameters between reports.

The Web Report Designer lets the user change the size of a TextBox inside a Table cell from its Properties. The change is also visualized in design time. For example, if the TextBox is enlarged, it sticks outside the table.

The above change is not respected in the preview of the web designer.

I would expect such a resize to be impossible, as in the Standalone Designer; or the entire table column/row to change its size accordingly.

When the WinForms Report Viewer is initialized from within the Form.Load Event, and the RefreshReport() method of the viewer is invoked before it is added to a parent form, the following exception will be thrown: 

Telerik.ReportViewer.WinForms.Licensing.UiLicensePresenter.ShowWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.Common.TelerikLicensePresenterBase.PresentWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.WinForms.WinViewer.OnPaint(PaintEventArgs eventArgs)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lpa

Please add ability to show vertical line markers on a Line series graph as show in attached file.

The expression language leaves much to desire, especially when working with object models. The most irritating is the iif function that evaluates all expressions, that forces to write user functions every time a method on an optional object should be called.
Ideally the scripting/expression engine is based on c# and/or vb compiler.

avatar 
Mike 

Posted 15 hours ago 


Is it possible to add the ability to assign a Style Name via Conditional Formatting in a future release of Report Designer in the Reporting Tool?  We are using the Style Names for consistency with regards to fonts, sizes and padding.  The ability to use the already existing Style Name as the Conditional Formatting result would be much simpler than having to recreate all of the Style Name's properties. 

Hi there, It would be nice if the vector images included in reports could be preserved when exporting as a PDF. I have some emf images which I use in our reports and when viewing everything is lovely vector, as soon as I export it though the image is converted to a bitmap.

As a developer that uses both Telerik Data Access and Telerik Reporting in its projects, I often find myself in a situation where I experience version mismatch errors regarding the Telerik.OpenAccess.* assemblies. For me it is inconvenient to downgrade the version of Data Access, and would like to either be able to automatically add the binding redirects in the .config file, or to use a more recent version of Data Access in my Reporting applications.

I'm planning to use Telerik Reporting as the reporting soltion for a customer portal that I'm developing. This portal will be sold to multiple customers and amongst other things the customers will be able to add their own reports that they will build using the Stand Alone Report Designer.
Please consider adding a Query Builder, similar to what is in the Visual Studio version of the Report Designer to the Stand Alone Report Designer as this will greatly enhance the user experience and negate the need to use other tools to build the queries, especially as many end users would not have access to tools such as SQL Management Studio, etc.

Regards

Edu

Need a way to export a drill down report with the visibility toggles as they are set in the Reportviewer.

Currently, if row visibility is something other than the default, if you export a report using the suggessted method:

Dim result As Telerik.Reporting.Processing.RenderingResult = _
		reportProcessor.RenderReport("PDF", ReportViewer2.ReportSource, New Hashtable())

Using fs As New System.IO.FileStream(filenamePDF, System.IO.FileMode.Create)
    fs.Write(result.DocumentBytes, 0, result.DocumentBytes.Length)
End Using
 
It loses the user defined visibility and exports the default.

If you use the Reportviewer.ExportReport() call, the report retains it's visibility, HOWEVER it prompts a file save dialogue. Unfortunately we cannot allow file browsing for our clients.

If we simply had an option with ReportViewer.ExportReport() to specify the file path to save to (preventing the file dialogue from popping up), this would be a non-issue.