Breadcrumbs

How-to - Clear test mappings following a clone

Aim

There may be some instances in which data for a destination connection needs to be cleared. For example, after cloning a ServiceNow Production instance to a Dev/Test instance.

CI Sync destination connections for Test environments can have their Ignored Records, Searchkeys, and Mappingscleared from CI Synchronizer.

If data needs to be cleared from connections for Production environments, please Contact Us.

This KB applies to:

Applies to Versions

All

Applies to Source Connectors

All

Applies to Destination Connectors

All

Process

Clearing Data

  1. Navigate to Settings and open the Data tab.

    1. Destination connections and record counts should be displayed.

image-20241031-034542.png

  1. Click Clear Data. You will then be prompted to confirm data deletion

    1. This will remove Mappings SearchKeys and Ignored Records from CI Synchronizer.

    2. Jobs using this connection will NOT run until clearing is complete.

image-20241031-035116.png

  1. Once confirmed, the system will begin deleting data.

    1. The record counts on the page will update periodically as the deletion progresses

image-20241031-035646.png


CI Sync does NOT implement Search Keys for Software Instance (cmdb_software_instance) or Patch (cmdb_ci_patches) recordsets. If you clear the mapping records from CI Sync while records remain in the cmdb_software_instance or cmdb_ci_patches tables, CI Sync won’t correlate to these existing records and duplicates may get created in ServiceNow.

To avoid this, clear out any cmdb_software_instance and cmdb_ci_patches records from ServiceNow.


There are currently no related articles.

Control Information

Created

Reviewed

Data Classification

PUBLIC
Classified in accordance with the Syncfish Data Classification Framework