List of preservers and exclusions tables for cloning

Release version: Zurich

Updated July 31, 2025

3 minutes to read

Summarize

Summarized using AI

Summary of List of preservers and exclusions tables for cloning

When installing Service Exchange on a cloned ServiceNow instance, specific tables must be preserved or excluded to maintain proper connectivity and functionality. Using the default system clone profile may result in loss of critical Service Exchange data. To avoid this, customers should create a custom clone profile tailored to Service Exchange requirements.

Show full answer Show less

This involves removing certain cleanup scripts and validating the inclusion of key Service Exchange tables within the profile’s preserver and exclusion lists. After cloning, connections must be reestablished and Capture Definitions reactivated to restore full Service Exchange operations.

Clone Profile Configuration for Service Exchange

Create a custom clone profile via All > System Clone > Clone Profiles and select New.
Remove the Remote Process Sync Disable Records script from the Cleanup scripts list.
Ensure Service Exchange tables are properly included in either the Preservers or Exclusions lists according to the provided specifications.

Impact of Preservers and Exclusions on Clone Behavior

The clone operation’s effect on tables depends on their inclusion in the preserver and exclusion lists:

Preserver Table	Exclusion Table	Result on Target Instance
Included	Included	Existing data on the target is retained; no records are copied from the source.
Included	Not included	Target retains existing records and adds new records from the source; existing records are not overwritten.
Not included	Included	Target table is emptied; no data copied from source.
Not included	Not included	Target table is replaced entirely with source data, overwriting existing records.

Preservers and Exclusions Tables for Service Exchange

Customers must update their clone profile’s preserver and exclusion lists to exactly match the Service Exchange tables specified. This includes various catalogs, sync definitions, error codes, tasks, connection settings, and user criteria related to Service Exchange provider and consumer roles.

The tables are categorized into Global, Provider, Consumer, Remote Process Sync, Transport, Transporter, and Employee Profile groups, each with designated preserver and exclusion lists to control cloning behavior.

Practical Examples

snsbservicebridgesettings (in both lists): preserves connection settings on target without overwriting them from source.
snsbconentitlement (preserver only): target retains existing entitlements and adds new source entitlements.
snsberror (exclusion only): target’s error records table is cleared and not populated from source.
snfdsoffering (not included in either list): target table data is fully replaced by source data.

Key Outcomes

Customized clone profiles ensure critical Service Exchange data is maintained or refreshed appropriately during cloning.
Maintaining accurate preserver and exclusion lists preserves connectivity, configurations, and data integrity post-clone.
Reestablishing connections and reactivating Capture Definitions after cloning restores full Service Exchange functionality.

When installing Service Exchange, certain tables must be preserved or excluded to maintain connectivity after a clone.

If the default system profile is used, some of the Service Exchange table data isn’t preserved. To address this issue, you must create a custom clone profile with specific settings required for Service Exchange. Navigate to All > System Clone > Clone Profiles and select New to create a custom profile. For more details on clone profiles, see Create a custom clone profile. In this profile, you must:

Remove the Remote Process Sync Disable Records script from the Cleanup scripts related list,
Validate if the following Service Exchange tables are included in the custom profile.

Note:

After a clone, you must reestablish the connection and activate the Capture Definitions. See Reestablish connection after a clone for a provider and Reestablish connection after a clone for a consumer.

Service Exchange tables to preserve and exclude

The following scenarios describe how clone operations affect table data based on table configuration in the preservers and the exclusions tables list.

Table 1. Clone operation results by table configuration
Preservers tables	Exclusions tables	Result on target instance
Included	Included	Target table retains existing data. The system preserves existing records and copies no records from the source.
Included	Not included	Target table retains existing records and receives additional records from the source table. The system does not overwrite existing records.
Not included	Included	Target table is empty after the clone. The system discards existing target records and copies no records from the source.
Not included	Not included	Target table contains only source table data. The system replaces all pre-existing target records with records from the source.

Update the Clone Profile Preservers and Exclusions lists to include only the Service Exchange tables specified in the following preservers and exclusions tables. Add any missing tables from the specified lists and remove any Service Exchange tables that are not included in these lists.

Table 2. Preservers or Exclusions table
	Preservers table	Exclusions table
Global	catalog_ui_policy catalog_ui_policy_action ih_sync_capture_definition ih_sync_definition ih_sync_inbound_definition ih_sync_outbound_definition ih_sync_process_event ih_sync_remote_system item_option_new sc_cat_item_catalog sc_cat_item_category sc_cat_item_user_criteria_mtom sc_cat_item_user_criteria_no_mtom sc_category scan_finding scan_task sn_sb_con_entitlement sn_sb_error sn_sb_known_error_code sn_sb_con_provider_connection sn_sb_con_provider_task sn_sb_release sn_sb_remote_script_approval sn_sb_rps_connection sn_sb_service_bridge_settings sn_sb_transform_line sn_transport_queue	ih_sync_capture_definition ih_sync_definition ih_sync_inbound_definition ih_sync_outbound_definition ih_sync_process_event ih_sync_remote_system scan_finding scan_task sn_sb_error sn_sb_pro_persona sn_sb_remote_task sn_sb_rps_connection sn_sb_service_bridge_settings sn_sb_transform_line sys_alias
Base	sn_sb_authorized_user sn_sb_error sn_sb_identity sn_sb_known_error_code sn_sb_provider_task sn_sb_release sn_sb_remote_script_approval sn_sb_remote_task sn_sb_scratchpad sn_sb_service_bridge_settings sn_sb_transform_line	sn_sb_authorized_user sn_sb_connection sn_sb_entitlement sn_sb_error sn_sb_identity sn_sb_provider_task sn_sb_remote_record_producer sn_sb_remote_script_approval sn_sb_remote_task sn_sb_scratchpad sn_sb_service_bridge_settings sn_sb_transform_line
Provider	sn_sb_pro_authorized_user sn_sb_pro_consumer_connection sn_sb_pro_entitlement sn_sb_pro_provider sn_sb_pro_provider_task sn_sb_pro_registration sn_sb_pro_remote_choice_definition sn_sb_pro_remote_record_producer sn_sb_pro_remote_service sn_sb_pro_remote_task sn_sb_pro_remote_task_variable sn_sb_pro_service_bridge_settings sn_sb_pro_transform	sn_sb_pro_inbound_field sn_sb_pro_outbound_field sn_sb_pro_provider sn_sb_pro_registration sn_sb_pro_remote_record_producer_consumer_criteria sn_sb_pro_remote_task_def sn_sb_pro_remote_task_def_consumer_criteria sn_sb_pro_remote_task_variable sn_sb_pro_transform
Consumer	sn_sb_con_authorized_user sn_sb_con_consumer sn_sb_con_entitlement sn_sb_con_inbound_field sn_sb_con_outbound_field sn_sb_con_provider_task sn_sb_con_remote_record_producer sn_sb_con_remote_task sn_sb_con_remote_task_def sn_sb_con_remote_task_variable sn_sb_con_service_bridge_settings sn_sb_con_transform	sn_sb_con_consumer sn_sb_con_inbound_field sn_sb_con_outbound_field sn_sb_con_persona sn_sb_con_remote_task_def sn_sb_con_remote_task_variable sn_sb_con_transform
Remote Process Sync Transport	sn_sb_rps_connection (Provider only)	sn_sb_rps_connection (Provider only)
Transporter	sn_transport_profile* sn_transport_queue*	Na
Employee Profile	user_criteria sys_alias sys_user sys_user_has_role

"*" - Applicable for both provider and consumer.

The following scenarios describe how clone operations affect table data based on table configuration in the Clone profile preservers list and the Exclude tables list.

The following examples use tables from this page to illustrate each scenario:

sn_sb_service_bridge_settings (included in both lists): The system preserves connection settings you configured on the target instance after the clone. Settings from the source instance do not overwrite them.

sn_sb_con_entitlement (included in Clone profile preservers only): The target instance retains existing entitlement records and receives additional entitlement records from the source instance.

sn_sb_error (included in Exclude tables only): The error records table is empty on the target instance after the clone. The system discards error records that existed on the target and copies none from the source.

sn_fds_offering (not included in either list): The system replaces the target table with source data. Records that existed on the target instance before the clone are replaced by source instance records.

Preservers and exclusions tables

Zurich Service Exchange