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.
I think navigating over pages by click is boring/complicated, scroll over pages seens to be the standard in the majority of applications.
I know that the HTML5 ReportViewer has the pageMode() property to solve this...
There's a way of implementing the PageModeProperty into the WPF ReportViewer?
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.
I set globally the culture on the Linux Ubuntu Docker Container. Interestingly, the negative currency with en-US and fr-CA was displayed with the '-' sign rather than in brackets.
This was reproduced even in the values set with the Text Function FormatWithCulture(cultureName, format, args). The function displayed wrong formatting also on Windows, even in the Standalone Report Designer for .NET 8.
When the global culture on Windows was en-US, the negative decimal value formatted without the FormatWithCulture function was displayed correctly in .NET 8.
In the .NET Framework, the negative currencies were displayed as expected in all scenarios.
I have linked also a muted video showing the issue.
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
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.
We have developed additional logic around the Telerik Reporting Engine so I don't know if this would be valuable to anyone else or not but I would love to have the ability to associate custom properties to a control. The use case that comes to mind most is the logic we have implemented to auto size text that displays on a report to fit in the area provided. We use a control naming scheme to determine what controls should be auto sized and how they should be sized in relation to other parts of the report. It is typically assigned used with a Panel, a TextBox, or an HTMLTextBox. I would love to have the ability to add two associate two additional properties to these controls that could be used in the stand alone designer to allow users to set an AutoSize (true / false) and a SizingGroup (string) property on these controls rather than worry about making sure the control is named properly. I would allow users to more easily leverage this functionality. I realize that it is unlikely that this will be implemented since it wouldn't be widely used but I like to dream.
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.
Create new parameters control (as same included in report viewer controls for WebUI, WinUI, ...); to provide the ability to gathering user values but without rendering the report. It will help scheduling and background generation of reports.
When converting Crystal Report templates (rpt files) to Telerik Reporter templates it would be very helpful to include the schema settings in the associated ttx file which provides the dataset info. This allows the layout to map properly to the converted template. Also any imbedded SQL statements found in the Crystal template could be captured and the conversion wizard could then query the developer on database connection requirements. These two abilities would make conversion a complete tool allowing rapid deployment of new Telerik report templates.
Datasources of tables and expressions are processed even when the item is not visible. This can lead to performance problems. It should be possible to disable certain items to be processed. The most obvious way is that items are not processed, that are not visible anyway.