The autumn update for the report generator is now available! The functionality of our solutions is expanding every day and we are pleased to present you a partial integration with FastReport Cloud, .NET 7 support, JasperReports template converter, connection to stored procedures in MsSQL, and much more.
FastReport .NET, FastReport Core, and FastReport Mono now support some interaction experience with FastReport Cloud.
Now you can download the report from Cloud and work on it in the designer, or vice versa — upload your files to Cloud.
A web preview function has also appeared in addition to the standard preview. The report can only be viewed this way if it was opened from Cloud.
FastReport Cloud can store connections to data sources. From now on, you have the option to add these data sources to your report.
It also became possible to add the connection to Cloud.
Read this article to learn more about the new features.
We have added .NET 7 support for FastReport.Core and FastReport.CoreWin. This platform improves application performance and adds many new features to your projects.
Now the report validator runs in a single thread. The speed of its work is significantly optimized. You can notice the changes in processing reports with a large number of errors. While the validator is checking the report, the check window shows a respective message.
In this case, you can edit the report. A table with errors will appear upon completion of the validator.
For convenience, we have added a new column with error numbers. Its display can be enabled or disabled via the table context menu. In the same way, you can customize the display of the error type column.
We have added the option to convert report templates from JasperReports to FastReport .NET templates. JasperReports reports may contain objects that are not supported by the FastReport designer. These objects will not be converted or will be replaced to make the generated report as similar as possible to the one created in JasperReports.
The MSChartObject object has many properties and settings. The most frequently used ones are moved to the object editor. Properties that are not available in the editor can be modified using the Object Inspector. However, there was a problem with these properties — when they were changed, the report was not seen as modified. As a result, saving was not available.
To save the report, it was necessary to change its other property or object. In addition, the values of the specified properties were reset to their default values when preparing a report and after closing the preview window.
This bug has been fixed in the new version.
We have added the option to connect to procedures stored in MsSQL. This was previously available via a database query. Now you can connect to procedures much more conveniently using the interface of database table connection. They will be displayed in the selection window along with the tables.
Once you select a procedure, a window with parameter settings, if any, will appear. Read more in the article.
We have added a new PrintOptimized property and a corresponding option in the export window. Enabling this option will greatly increase the quality of the exported image. However, the size of the output file will be bigger.
We have added a new option, UseFileStream, for exporting to Excel 2007. It can only be used when exporting from code to a file. This option is useful when exporting reports with a large number of pages (several tens of thousands) in multiple threads. This will help you avoid memory shortage errors. In other cases, it does not make much sense to use it and it is not recommended to do it. Example:
You can now export the currency data format as an accounting format. To do this, a corresponding option has been added in the export window and the CurrencyToAccounting property.
We are upgrading the minimum supported version of FastReport .NET to .NET Framework 4.6.2 due to the following:
The full list of changes is available at the following link.