When I have a report that uses the Shape Report Item and I export it to Excel(XLSX) in Linux, upon opening the Excel file, I am met with the following warning:
We found a problem with some content in "Report.xlsx". Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes
If cells grow or shrink, if there are hidden cells, any time a report section grows vertically, the next section/table is not respecting the growing of the previous item and text prints in the wrong spot or the table overlaps the previous table.
A potential workaround is to manually convert the troublesome tables to lists where possible.
The DocumentMapVisible settings that I set in the initialization of the WPF Report Viewer are not respected.
I can hide/show these areas from the buttons in the report viewer's toolbar but am unable to have them hidden initially.
Currently, the only workaround is to set an event on this.ReportViewer1.RenderingEnd += ReportViewer1_RenderingEnd;
private void ReportViewer1_RenderingEnd(object sender, Telerik.ReportViewer.Common.RenderingEndEventArgs args)
{
this.ReportViewer1.DocumentMapVisible = false;
}
I installed the @progress/telerik-angular-report-viewer - npm (npmjs.com) package of version 19.23.718 in my project and noticed that the viewer's SASS template uses incorrect versions for its resource references.
<link href="{service}resources/font/fonticons-17.1.23.719.css/" rel="stylesheet" />
<link href="{service}resources/styles/telerikReportViewer-17.1.23.719.css/" rel="stylesheet" />For the template to work with a Reporting service of the latest version(17.1.23.718), the template must be edited.
When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.
The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.
I just migrated from building with react-scripts to Vite, as it seems react-scripts is deprecated. After the change, the react report viewer is not functioning correctly. Browser console shows:
Instantiation of Kendo TreeView as Document Map threw an exception TypeError: $kendoHtmlEncode is not a function
Uncaught (in promise) TypeError: $kendoHtmlEncode is not a function
I have cascading parameters, and in some cases, the data set for the dependent parameters is empty. In these cases, the parameter editor of the second parameter is displayed as an input/textbox rather than a dropbox without data.
In the Standalone Designer, the parameter editor is displayed as expected, with a dropdown without data.
The report for reproducing the issue is Product Line Sales-01.zip
Hi,
I use Azure App Service Linux to host my .NET CORE ASP Server with Blazor as Frontend.
There is a way to embed Fonts using the telerikReporting / privateFonts configuration part. But as an application intended for multiple users (using different copies of Azure App Services), this is not a proper solution.
My idea whould be, to allow my client, who designs their own template using Telerik Report Designer (Standalone) (baed on many premade templates from my programm), to allow to embed their own Fonts from there, and upload the TRDX file to my server and let it render. Note that I use Telerik Reporting only in Backend and returns only rendered PDF files to the client (font end)
In short, allow TTF / OTF Font embedding in Telerik Report Designer, store it INTO TRDX / TRDP files.
Thanks
Vulpes
There is no way to send a bearer token with the requests to the reporting service made by the native Blazor Report Viewer because the viewer does not expose a property for setting the token.
The background image of a report item is not sized correctly when exporting in PowerPoint format (PPTX) and have the UseMetafile flag set to false.
If the flag UseMetafile is set to true, the image is rendered as expected.
We have an application that is generating very large reports in "Print Preview" mode.
When the first page of the report is generated the Export button gets enabled. If the user does not wait for the report to be fully generated, and clicks the Export button, it doesn't do anything. We have also seen the application crash after clicking the Export button while the pages are loading.
When I conditionally hide a TextBox in a table, I got unwanted spaces between the hidden boxes.
In my example below I have 30 records as seen in the first table.
In the second table I have the same data, but conditionally formatting it to hide based on the following:
= Fields.Column1 > 2 and Fields.Column1 < 28
Notice the space that shows between 02 and 28.
After dragging a report viewer control from the Visual Studio toolbox to the surface of a Windows Form, the viewer is added to the component tray but it is not added to the Controls collection of the form. Thus, the viewer is not displayed when running the application.
Also, some properties of the report viewer, such as the ReportSource property, are not serialized properly after being modified through the Visual Studio properties window.
Currently, one can work around these issues by manually editing the InitializeComponent component method of the form's .Designer.cs file.
Hey team,
Please kindly speed up about this bug as this affects the project alot. Also would appreciate for the update.
In a cascading dropdown, we noticed that the child dropdown is not populated until the parent dropdown is closed after selection. There is a second delay between selecting the parent dropdown and populating the child dropdown. Between this small interval of time, the preview button can be clicked, as it is not disabled, due to which wrong values (previously selected values) are passed in the parameters resulting in incorrect results.