Execution Filtering Options: Re-run Execution For Errors Only

Sometimes, you may get some errors in a migration project. Once the cause of these errors has been identified and corrected, you may want to run the project again to correct them. However if a large number of records are migratedlwhen the project is executed, it maytake a long time to run the entire project again, just to correct a handful of errors.

In this situation, you can re-run the project just for the records that reported a warning or error.

This can be configures in the Execution Settings on the Filtering tab.

If you execute the Project for the very first time, or want to migrate all records. the Filter based on Failures during previous migration option should be unchecked, as it will be by default.

Note that to be able to use a report from one execution to identify the error records to rerun next time, ont the first run reporting needs to be configured to write to either database or CSV. See the section Migration Reports for more information.

Note that the Web Reporting option alone will not be sufficient to provide the reporting input to identify the records where an error occured.

If you then execute the same project and only want to process the error records then check Filter based on Failures during previous migration option and configure these options..

Configuring the Filtering Options

The followig should be noted:

The CSV option will only be enabled if the 'reports' folder can be found in the project folder. This will not be the case before the project is run for the first time. The CSV option will be checked by default if it is enabled.
The Database option will only be enabled if the project has the report database configured in Report Target tab in Project Properties.
Select the latest execution timestamp from the list in Execution Identifier. Only executions where reporting data was generated will be listed.
Check the Include Warnings checkbox if the records with warnings as well as errors need to be included in the re-run.

Example

Below snippet shows an there were 10 error records with 34 records being created sucessfully. The execution reporting was configured to write results to a database.