This section describes how to migrate reports from existing reporting tools to ClientUI Reporting. ClientUI Reporting is currently able to convert reports from Crystal Reports (requires build 13.0.2000.0 or later).
Please keep in mind that the converter is just a helper utilities to save some time instead of re-creating it. It does not guarantee a one-to-one complete conversion due to structural differences between ClientUI Reporting and other reporting products, and not all of the report objects have it's counterpart in ClientUI Reporting end. The same goes for scripting, event, and complex logic, which will be written 'as is'. You would need to review and fix the reports manually to achieve the desired results.
Running Conversion Tools
To convert reports to ClientUI Reporting, follow these steps:
- Open a Command Prompt window.
Look for the ReportConverter.exe, which should be located in C:\Program Files (x86)\Intersoft Solutions\ClientUI 12\Tools\
Specify your report file path as the command argument.
You can also specify a wildcard if you have more than 1 report to convert.
The output result will be written by default with the same name but different extensions (.xaml). However you can change it by specifying the second argument, but it is valid only with single file name in the first argument.
Now what you need to do is to review and fix the output result. The following list represents the common problems when converting the reports.
The tools convert only the data definitions. If your report need a datasource, then you need to provide the data provider. To learn more about report data provider, see Data Provider Overview topic.
Currently there is no way to extract image source stored in report template, especially from Crystal Reports, so the result image will be left empty.
Not all of the scripting, event, and complex logic can be converted. Most of them will be written 'as is', so you will need to re-write it using ClientUI Scripting. Please refer to Scripting Overview.