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
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:
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 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
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.
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.
The Initialize method in ReportViewer.cs is called from both the OnLoaded and OnApplyTemplate methods, which in turn calls the AttachModelEventHandlers method. This leads to it adding the event handlers to the model twice every time it is loaded. The DetachModelEventHandlers is only called once (in the OnUnloaded method), so if you keep unloading and reloading the control, it adds 2 event handler invocations but removes only one. This means each one is called at least twice (if you have only loaded the control once), then 3, 4, 5, etc times if you keep unloading and reloading it.
I've worked around this by adding code to my wrapper class to prune the duplicated handlers for now, but this needs fixing in the base code.
If you add transparency to a Graph line, for example, the Y-axis, with an alpha value: '150, 255, 255, 192', it is respected in the Standalone Report Designer, where the rendering format is Image.
In the Web Report Designer and in the HTML5 Report Viewer preview, the alpha value is ignored, and the color is rendered as '255, 255, 192', which removes the transparency.
In MSSQL, you may use syntax like 'StoredProcedureName;1' to indicate stored procedure versioning, but it is not yet supported by Telerik Reporting.
I use such syntax and need to remove the version to make this work in Telerik Reporting.
It would be great if you also added support for versioning in MSSQL stored procedures.
Using the text-indent CSS setting results in part of the text on the first line being cut off:
I have a crosstab with a dynamic number of columns (time periods) that can exceed 15-20 columns. When exporting the report to PDF in A4 landscape format, excess columns are truncated and never printed on additional horizontal pages.
The issue is related to the Crosstab property 'RowHeadersPrintOnEveryPage'. When set to True, it places additional row headers on each page when using physical pagination. I suspect these additional headers are not taken into account when calculating the necessary page area, hence the final part of the Crosstab is skipped.
As soon as I reference a .NET 10 assembly containing models, there is a null reference exception that does not appear in EventViewer or Fusion logging at the opening of the Standalone Report Designer for .NET.
Here is a link to a muted video demonstrating how adding assembly references using the UI successfully adds the custom assembly to the designer, as well as the bug when removing the assembly version.
Hello Team Support,
I work with the ReportViewer in WPF. I modified the description of some format in my App.config.
When I export my report, if the description is too long, it does not fit the message window anymore.
Here is a screenshot of my issue:
Thank you in advance.
Best regards,
Jonas
When my application is hosted on Windows, Arabic date values appear reversed in the day part during PDF export with the Skia graphics engine. For example, 2025/01/01 is displayed as /01/10 when Arabic digits are used.
With the GDI graphics engine, the Date values are rendered as expected.