Unable to create Clone Profile Exclusions or Clone Profile Preservers for non-Global/scoped application tables - Known Error

Unable to create Clone Profile Exclusions or Clone Profile Preservers for non-Global/scoped application tables Description Unable to create Clone Profile Exclusions or Clone Profile Preservers for non-Global/scoped application tables

Steps to Reproduce

Example 1 Create a new Clone Profile (clone_profile) record. Create a Clone Table Exclude (clone_data_exclude) record or a Clone Data Preserver (clone_data_preserver) record for a non-Global/scoped table. i.e.: 'cmdb_ci_cmp_cloud_account' in the "Cloud Management Platform" scope Navigate to the Clone Profile record, and click "Edit" for either the "Exclusions" or "Preservers" related lists. Expected behavior: The table added as an exclude or preserver in Step 2 is displayed in the "Available" side of the slushbucket to be able to be added to the "Selected" side, as is the case with Global exclude and preserver records.

Actual behavior: The table added as an exclude or preserver in Step 2 is not displayed and does not have a record on either the Clone Profile Exclusions (clone_profile_exclusions) or the Clone Profile Preservers (clone_profile_preservers) tables.

Additional Example 2 When creating a new Clone profile, it picks up all Exclude table configurations by default but it is missing the following tables:

digest_properties idp_certificate saml2_update1_properties sso_federation sso_properties These tables can't be selected for exclusion from the slush bucket.

Workaround To add affected tables to the exclusion list in clone profile for Example 2 :

Delete these 5 tables from the Clone Exclude Tables list: /clone_data_exclude_list.do?sysparm_list_mode=grid&sysparm_query=nameINdigest_properties,idp_certificate,saml2_update1_properties,sso_federation,sso_properties&sysparm_offset= Add these tables back to the Clone Exclude Tables using the new button on the list view of the table: /clone_data_exclude_list.do Once the tables are added back, these will now belong to the GLOBAL package and you should now be able to add these tables in the Exclusions list of clone profile using the Edit button. Note 1 : If you had already cloned over, using a clone profile that was missing these tables, you should rollback your previous clone and then submit another clone to have the records in your target instance in the expected state.

Note 2 : We do not have a workaround to add Preservers which are in a different scope, therefore if you are missing preserver records in your clone profile then you will need to revert back to the old functionality by scheduling the clone with the Profile field empty.