Source Deletion Behaviour with Skipped Records

Scope: ServiceNow->Database and ServiceNow->ServiceNow projects only

If you have configured source deletions and also set the option 'Entry Exists on Target' to Skip Entry, then If a record is ‘skipped’  due to existence on target, it can still be deleted. 

A ‘skip’ caused by any other means (e.g. a no match action in a lookup mapping) would result in the deletion being prevented. This is to allow users to migrate records in the correct hierarchical order, using inclusion filters, then have mappings to delete them in the opposite order to avoid cascade deletions.

 For example you might have 3 mappings to archive Companies and their Business Units::

1. Migrate Company Records (with no source deletions configured);
2. Migrate Business Units for these companies and delete source records;
3. Migrate Company Records, skipping updates and creates (to save time – only the key mappings would need to be specified) and Delete those that have no business units that will be cascade deleted.