Tips to run Crystal Reports in Report Runner

Run Datapipe reports

You need to copy the associated dll for the datapipe report to the EBxxA customisation directory and update the ebrpt.ini file with the data query.

For details refer to: Run Datapipe Reports in Report Runner

Reports with Temp tables

Report Runner does not trigger processes which populate temporary data structures required by certain reports (such as AR Statements). Running reports of this nature requires Orchid’s Extender module and one or more suitable custom scripts to trigger the processes.

Contact Orchid support if you are unsure about specific reports in Sage 300 or Third Party Modules.

Crystal Report Parameters

In the Sage 300 report object, all parameters must be defined as strings. So all the parameter values will be passed from the Report Runner input screen to the associated Crystal Report as a string. Hence it is best that the parameter in the Crystal Report is set to be the same type - as string - and then converted into appropriate data type for the report within the Crystal Report itself.

The following guidelines are recommended for the parameter name in any Crystal Report being called by Report Runner :

Crystal Report parameters need to be:

• Set as STRING

• Parameter names need to be all UPPERCASE

• Parameter Name cannot contain spaces

Report Runner Prompts all the Crystal Parameters

If the Crystal Reports "Enter Parameter Values" screen pops up when you run a report, check that the Customization Directory in Sage 300 Administrative Services and in I/M Options > Report Runner are pointing to the same folder.

For details, refer to Configure Report Runner Tab in I/M Setup / Options

Example in Troubleshooting Report Runner for Crystal Reports