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.
If you do a Excel export, it renders the headers value, which we set with an expression (customer specific localised text), but as CSV the header names/IDs are used. It would be nice to have a 'Export Settings' category on the page properties, see attachment for example. Also shows another useful feature of disabling export option easily per report.
we changed our reporting service to .NET Core and now the Backgroundcolor for some alternating lines are not visible in HTML5 viewer.
In exported PDF they are...
I change the backgroundcolor from custom like <Style BackgroundColor="240, 240, 240" /> to <Style BackgroundColor="Control" /> which is working fine.
But i can see difference in color of HTML5 report and pdf report.
What can i do to have it working like before, i mean i want to use it like this again <Style BackgroundColor="240, 240, 240" /> if possible.
PS:We are running our service on a Linux Docker-container
The ObjectDataSource component in the Web Report Designer does not have complete design-time support. The major things that are missing:
The Margins property cannot be set in the Blazor wrapper of the Web Report Designer:
This is a feature request to allow a designer to set the locale at preview time.
We work on reports that are deployed and executed in many regions and locales around the world.
We cannot have our report designers switch the locale each time they need to test or validate a report, it would become too cumbersome.
Would you be able to add an option (default: Current locale) to the "Preview" screen in the designer that allows the report designer to set the locale to Preview the report as.
I like the new open dialog for the Web Report Designer, but now my report names are all truncated and I can't tell what anything is. Can you please off a list view in the Open Dialog so all my names aren't "Company R..."
One of the main features the clients require when exporting the reports to XLS or XLSX is to have the page width already set to 1 page. But for none of these exporting options, this is possible, unless you intercept somehow the export functionality prior to rendering the document to the client
Do you have an updated road-map or plan to support Web assembly (WASM), especially Blazor? You already published Blazor articles in your blogs.
It will be a good idea to add a new report viewer based on Blazor, protecting the parameters between the viewer and its API controller.
Also, will be a very good idea to start your online report designer (like alternative products), based on web assembly
We'd like to distribute the standalone report tool to our clients and provide data through a web service. We don't want to have to redistribute a dll everytime we make new data available. The standalone report tool should be able to query our webservice for what data is available and then allow the client user to create reports from it. i.e. obtain list of table names dynamically as well as their column names and data. A possible solution is to allow the tool to view and interact with classes in an external assembly that are dynamically generated with Reflection.Emit.
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
The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.The workaround is to avoid using the SQL DataSource wizard and edit the data source properties directly in the properties grid. You can check the attached silent video that demonstrates how to do so.
I can see that we can operate over a file definition using save, open, and save as. It would also be nice to be able to download the report definition as well.
At the moment it's only possible to have your reports in old-fashioned projects.
It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).