Provide NuGet package with UI for WPF NoXaml dependencies for adding it to the project that hosts WPF report viewer:
Telerik.Windows.Data.dllPrint functionality doesn't work in React application.
Steps to reproduce:
1. You may use the sample project from How to use HTML5 Report Viewer in React Application article.
2. Run the project and click on Print.
The following error can be seen in the browser's console: Resource interpreted as Document but transferred with MIME type application/pdf: "https://demos.telerik.com/reporting/api/reports/clients/a7fdd020ec4/instances/3f53abd1614/documents/c3923e685e6d6ebefb3d11?response-content-disposition=inline".
When the Report is shown in the HTML5 Interactive viewer, you can move the mouse over the cells in the Hyperlink column. When a cell has the mouse cursor hovering over it, a gray border is drawn around the cell.
The problem is that this gray border is partially covered by the Background color of the next cell.
Hi there,
I was wondering if you had in the Pipeline/road map a Report Designer integrated into Visual Studio for .NET Core?
And also if there is an ETA?
If I can add my +1 to this would be appreciated.
Regards,
Mark
Data Explorer of the Report Designer does not refresh the schema on the Refresh button click when the Stored Procedure used in a SqlDataSource component is modified.
You need to reconfigure the data source component, for example, just open the Data Source Wizard and click Finish, or close and re-open the report for the actual refresh.
My report consists of a Report Header and a Detail section. Their design-time height is totally less than 20mm. There are no PageBreaks or GroupPageBreaks and all KeepTogether properties are False. In Print Preview, the Detail section starts from the second page when the PaperSize Height is 88mm or less. This is not expected as there is sufficient space left after the Report Header. The Detail section starts rendering from the first page only when the paper height is more than 88mm, which is the expected behavior.
See the forum post Report Header and Detail Section does not print together for the report definition that allows reproducing the issue.
When exporting to Excel Worksheet, the CheckBox item is rendered as Excel Picture. If the machine settings are higher than the default 96 DPI (100%), the checkbox image is generated with incorrect size and the produced Excel file is corrupted.