Build and Deploy Copy Field Enrichments from a Data 360 Sandbox

Use Data Kits and Change Sets to package and deploy tested copy field enrichments from your Data 360 sandbox to a production environment.

To create, test, and deploy copy field enrichments in a Data 360, use these steps.

1. In a sandbox org, create a copy field enrichment.
2. Test the copy field enrichment in the sandbox.
3. To package the enrichments, create a DevOps data kit and complete these steps.
4. 1. Follow the first two steps in Deploy Data 360 Changes Across Orgs.
   2. On the Data Kit Contents page of your data kit, go to the Copy Field Enrichments section, and click Add. Then, select the copy field enrichments that you want to deploy.
   3. Link the data kit to an outbound change set by following step three of Deploy Data 360 Changes Across Orgs.
   4. In substep 5 of step 3 of Deploy Data 360 Changes Across Orgs, add all of the copy field enrichment’s dependent components to the change set.
   5. Follow step 4 of Deploy Data 360 Changes Across Orgs to complete the deployment.

After you deploy the inbound change set to a production org, you can find the copy field enrichment in Object Manager under the supported object’s list of Data Cloud Copy Field Enrichments.

Deployment Considerations

When deploying copy field enrichments and related metadata, consider these details.

• If you deploy a copy field enrichment to a target org that already has an enrichment with the same definition, the deployment succeeds, but no changes are made.
• To deploy a data model object (DMO), your data kit must include either a data lake object (DLO) mapping or an associated data stream. To merge back relationships between DMOs or calculated insight objects (CIOs), ensure that the DMOs or CIOs meet this requirement, and that you add the Field Source Target Relationship to the outbound change set.
• Data 360 dependencies: you must manually add data streams or any relevant DLOs. If a CIO is required for the copy field enrichment, ensure that its dependencies (for example, DMO) are included.
• CRM dependencies: When adding items to a Change Set, custom CRM fields are automatically discovered. If needed, you must manually add custom CRM objects to the Change Set.
• Copy fields are always deployed in an inactive (draft) state. You must manually activate the copy field enrichments after deploying them.

Limitations

These actions are not supported for copy field enrichments.

• Deploying an updated copy field enrichment is not supported.
• Undeploy is not supported.