The property DataSources is internal in the Report class. When manipulating the datasources of a report it's easier to have access to this collection than to go through all the elements en report parameters to check for datasources
I am using the Blazor Web Report Designer on a page that is not the default route, i.e. "/". When I am at step 2 in the WebServiceDataSource wizard to add parameters, if I click the Add Parameter button it routes to the home page.
I believe this is caused by the href="#' empty route. Below is an animation of what I mean. This is also reproduced in the BlazorIntegrationDemo in the installation directory.
The default value of the report property SkipBlankPages is True and when there is an error in the report, for example, due to a problem with the connection to the database, the error message may be hidden as the report is not rendered at all.
The report should be rendered in order to display the error message also when SkipBlankPages is True.
Not sure if you are aware of this but the new property SkipBlankPages in 2021/R1 will result in a corrupt (unopenable) PDF/XLS if the report contains no data.
The output used to be a blank report.
This behaviour is fixed by setting the Value to 'False' but this now requires the developer to remember to set this value on each new report. Perhaps the default should have stayed as 'False' and those who wish to remove blank pages could set it to true.
We are aware the property is set to true by default.
We have now had to modify (and subsequently retest) > 100 reports.
The generator should probably not create a 'corrupt' file in these cases.
When using the Report Viewer under WinForms, Print Preview allows the user to scroll through all report documents. I.E., everything in the document map. However, when using the Wpf version you cannot. In the Wpf version, the user must use the Document map to select and scroll through each particular area. For large reports containing multiple documents, this is tedious. Please make the Print Preview functionality for the WPF control match that supported by the WinForms control.