Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

List of preservers and exclusions tables for cloning

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 . 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.

Preservers tablesExclusions tablesResult on target instance
IncludedIncludedTarget table retains existing data. The system preserves existing records and copies no records from the source.
IncludedNot includedTarget table retains existing records and receives additional records from the source table. The system does not overwrite existing records.
Not includedIncludedTarget table is empty after the clone. The system discards existing target records and copies no records from the source.
Not includedNot includedTarget 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.

 Preservers tableExclusions table
Global- catalog\_ui\_policy - catalog\_ui\_policy\_action - clone\_data\_exclude - clone\_data\_preserver - clone\_profile\_exclusions - clone\_profile\_preservers - 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\_persona\_group - 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 - sn\_fds\_pro\_consumer\_criteria - sn\_fds\_pro\_inbound\_offering\_item - sn\_fds\_pro\_offering\_item - sn\_fds\_con\_outbound\_offering - sn\_fds\_con\_outbound\_subscription- 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 - sn\_fds\_pro\_consumer\_criteria - sn\_fds\_pro\_inbound\_offering\_item - sn\_fds\_pro\_inbound\_subscription - sn\_fds\_pro\_offering\_item - sn\_fds\_con\_m2m\_company\_offering - sn\_fds\_con\_outbound\_offering\_item - sn\_fds\_con\_outbound\_subscription
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 Transportsn\_sb\_rps\_connection \(Provider only\)sn\_sb\_rps\_connection \(Provider only\)
Transporter- sn\_transport\_profile\* - sn\_transport\_queue\*N/a
Employee Profile- user\_criteria - sys\_alias - sys\_user - sys\_user\_has\_rolesys\_alias
Foundation Data Sync- sn\_fds\_data\_processing\_queue - sn\_fds\_offering - sn\_fds\_offering\_item - sn\_fds\_request - sn\_fds\_subscription - sn\_fds\_subscription\_item- sn\_fds\_data\_processing\_queue - sn\_fds\_offering\_item - sn\_fds\_subscription - sn\_fds\_subscription\_item
Foundation Data Sync for Providers- sn\_fds\_pro\_inbound\_offering\_request - sn\_fds\_pro\_offering - sn\_fds\_pro\_offering\_request- sn\_fds\_pro\_inbound\_offering - sn\_fds\_pro\_inbound\_offering\_request - sn\_fds\_pro\_inbound\_subscription\_item - sn\_fds\_pro\_offering - sn\_fds\_pro\_subscription - sn\_fds\_pro\_subscription\_item
Foundation Data Sync for Consumers- sn\_fds\_con\_offering - sn\_fds\_con\_offering\_item - sn\_fds\_con\_offering\_request - sn\_fds\_con\_outbound\_offering\_request - sn\_fds\_con\_subscription - sn\_fds\_con\_subscription\_item- sn\_fds\_con\_offering\_item - sn\_fds\_con\_subscription - sn\_fds\_con\_subscription\_item
Health- sn\_sb\_issue - sn\_sb\_health\_connection\_stats - sn\_sb\_health\_issue- sn\_sb\_issue - sn\_sb\_health\_connection\_stats - sn\_sb\_health\_issue

"*" - 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.