I'm using the WinUI Report Viewer in my .NET 8 WinUI3 desktop application. All my reports initially render and display correctly, however, when the user clicks on the Print Preview button to switch to the print preview view, it causes my app to crash. This only occurs when using Versions 19.1.25.521 and above of the Telerik.ReportViewer.WinUI package. If I roll the NuGet back down to versions 19.0.25.313 and below, my application happily switches between interactive and print preview view without error.
Interestingly, if I force the Report Viewer to start in print preview view (with ViewMode="PrintPreview" in the xaml), it displays without error (though the toolbar print preview button is not showing as being toggled). I can then also switch to interactive mode once without error by toggling the print preview button. However, if I then attempt to switch back to the print preview mode, it again crashes.
I have a .NET project. I tried to add a CS-based report to it using the Visual Studio item template. However, when I opened it, I encountered an error message, which wasn't helpful.
After reaching out to the technical support, I was told that the Visual Studio Report Designer was not supported in .NET projects, and the alternative was either to open the CS-based report through the Standalone Report Designer or use TRDP reports (recommended for new reports) instead.
It would be nice if there were some warning about this, as it would save me some time and confusion, as at first, when I encountered the error message, I took the assumption that something was corrupted with my project.
When the current thread culture is set to Turkish (tr-TR), the lowercase and uppercase conversion rules differ from English — especially for the letter "i".
In Turkish:
"i".ToUpper() → İ (with a dot)
"I".ToLower() → ı (dotless i)
Our assumption that the Telerik HtmlTextBox internally parses and maps HTML tags by converting them to uppercase. When the Turkish culture is active, this conversion causes tag names to break, which is not a valid tag, so ordered lists fail to render.
Best regards,
Denis
ADA Accessibility is a priority for our customers, so we are aiming to ensure logical tabbing order for keyboard users.
I've noticed that the RowHeadersPrintOnEveryPage attribute, while very useful for creating more readable PDF exports, seems to result in some strange screen reader behavior when set to True.
The first problem is with the strange tabbing order in the live environment. The second column header is the first to receive focus, followed by the remaining column headers, then the data fields under the first column receive focus in a vertical list, until finally the first column header receives focus. Without the default RowHeadersPrintOnEveryPage setting (False), the first column header is the first to receive focus, which is expected.
In addition to the wrong tabbing order, the RowHeaderPrintOnEveryPage causes the screen reader to announce the incorrect column associated with a particular cell. I use the Windows Narrator. Other screen readers may result in slightly different behavior.
The Telerik Web Forms Report Viewer Form VS item template does not install the Telerik.Reporting.Services.WebApi package. However, the controller created with this template has a using statement for it.
Steps To Reproduce
Expected behavior
The build succeeds.
Actual behavior
The build fails due to the missing package.
Screenshots
Currently, the is permission for disabling saving, but it disables only the "Save" button.
I would like to be able to disable the "Save As" button and keep the "Save" button active, or vice-versa.
The data source of my report contains grouping string values, among which are the '10000' and '1010Q'. These two values are always treated as the same string, and the corresponding records fall within the same report group, which is unexpected:
Use SqlDataSource SelectCommand xml element instead xml attribute - it allows to write complex sql requests in any tool and just put it into xml without changes and have it well-formatted and readable:
So, instead of
save it as
or even
WebReportDesigner (Blazor) - permission to restrict "Build new data connections" and allow to use only "Select from existing data connections".
It isn't required, but would be nice have button "Test connection" in the bottom enabled to verify predefined connection
This is related to Ticket ID 1699907.
Currently, the WinForm report viewer fetches configuration (specifically the connection string for any named connection strings defined in reports) directly from appsettings.json, however, it would be useful if the report viewer could take into account an injected IConfiguration since there are scenarios where the configuration may not exist in appsettings.json or a preferred or more up to date user selected value has been added to the configuration from a different source (such as a userSettings.json or secrets.json).
Some background of my use case:
I have a desktop WinForms application targeting .NET 8.0. It usesTelerik.Reporting 19.2.25.813 and Telerik.ReportViewer.WinForms 19.2.25.813 to display reports.Currently, the only way to set ObjectDataSource parameters as nullable is by typing this manually in the `DataType` property as follows:
Consider allowing to do this through the "Edit Parameters" dialog:
I use an approved government font for the reports. I have specified it in the `privateFonts` option of the report engine configuration. However, on Linux, it is not picked up during rendering. In FontForge, the font shows the following warning:
On Windows, it causes no issues.
I cannot localize the messages of the Angular and React report viewers using the suggested approaches:
The only alternative is to use the approach from the Localization of the HTML5 ReportViewer Explained - Telerik Reporting article, which I can do only by loading the string resources script in index.html of the SPA.