Reporting and Logging

The Execution Reports

Congratulations, you have performed your first migration!

Now you may want to see some detail about what was migrated, and if anything went wrong.

As soon as Precision Bridge completes a migration, the execution report is available in the lower section of the Execution View. 

This list, on the blue tab, shows, at the highest level, how many records got migrated, how many records could not be migrated (errors) and how many recorded a warning. A warning generally indicates the record was migrated, but something either went wrong or should be checked. An error means that the records were not migrated at all.

Navigating an Execution Report

OK, so what if there were errors? How can you get more details? First, double click the execution report. This will open the execution report and display (green) tab, with a summary of all the form mappings where data was migrated. This will show the error counts against each form mapping.

Double clicking a form mapping report in the list will show individual record migration reports for that form mapping. Included here will be the all-important error message that you can use to troubleshoot the issue. The error may be caused by either Precision Bridge itself (for example if a lookup failed to return any result) or it may be returned by the target server if the migrated record was rejected for some reason. To copy the error message or the id of the source/target record, double click on the row once more to view the entry in a dialog.

All execution reports are written to csv files (by default) in the project folder to allow them to be shared. It is also possible to configure reports to be sent to a Reporting Server. For more information about this, see the articles: Writing Migration Reports to Database Tables or Reporting to a Service Now Instance

The csv files are located in the project folder, inside the reporting sub folder. Each set of reports is in another sub folder with the timestamp of the execution as the folder name.

Execution Logs

Each Execution also generates an execution log. This can be opened at any time for the current execution using the 'View Log' button. For a completed execution, the log can also be opened from the loaded execution tab or execution report list. The log file is stored in the project folder, under the logs\execution subfolder. The file name is the timestamp for the execution. Execution logs might be requested by the Precision Bridge support team for troubleshooting purposes.

By default, only high level log messages and errors are written to the log. However, you can change this in the Reporting and Logging tab on the Execution Options dialog. Also, if you check the debug option, the target values, and temporary variable values for the first 100 records migrated of each form mapping will be added. This can be useful for troubleshooting mapping issues where it is not clear why the target values for complex mappings are not set as expected.