Migrate Code Extension from Sandbox to Production by Using a DevOps Data Kit
Use a DevOps data kit to move code extension deployments or batch data transforms created by using code extension from sandbox to production. When you add a batch data transform created using code extension to your data kit, the associated code extension is automatically included in the data kit. When your code extension references either data lake objects or data model objects, you must manually add the referenced objects to the data kit.
Validate your code extension deployments and batch data transforms created by using code extension in a sandbox. See Run Code Extension.
Step 1: Create a DevOps Data Kit and Add All Components
In your sandbox org, go to Data Cloud Setup.
Under Developer Tools, click Data Kits.
Click New.
For Data Kit Type, select DevOps.
Name the data kit and add an optional description, such as what it contains.
Save your changes.
Add code extension deployments, batch data transforms, or both to your data kit by using one of these options:
Option 1: Add Data Transforms
Click Add next to Data Transforms, select the batch data transforms created by using code extension that you want to migrate, and click Save.
When you add a batch data transform, the code extension it references is automatically included in the data kit.
If your code extension references data lake objects or data model objects, you must manually add the referenced objects to the data kit (see steps 8–9).
Option 2: Add Code Extension
Click Add next to Data Custom Codes, select your code extension deployments, and click Save.
If your code extension references data lake objects or data model objects, you must manually add the referenced objects to the data kit (see steps 8–9).
Option 3: Add Both Data Transforms and Code Extension
You can add both batch data transforms and code extension to the same data kit.
Add code extension directly only if it’s not already referenced by the batch data transforms you’ve added.
If your code extension references data lake objects or data model objects, you must manually add the referenced objects to the data kit (see steps 8–9).
If your code extension references data model objects, click Add next to Data Models, select the DMOs that your code extension references, and click Save.
If your code extension references data lake objects, click Add next to Data Lake Objects, select the DLOs that your code extension references, and click Next. Then, click Save.
Step 2: Review and Publish the Data Kit
Review the component list to ensure that all dependencies are included.
Check the publishing sequence to verify components deploy in the correct order: DLOs and DMOs deploy first, followed by code extension deployments, and then batch data transforms created by using code extension that reference them.
If you add both batch data transforms and code extension to the same data kit, ensure the publishing sequence is correct. Code extension must deploy before any batch data transforms that reference it.
Important
Click Publish to make the data kit available for deployment.
In your production org, go to Data Cloud Setup and click Data Kits.
Open your data kit, and click Data Kit Deploy.
To deploy the data kit, select a data space, and add the connection org details of the data bundle.
Click Deploy.
The deployments follow the order defined in the publisher org.
When you package and deploy DMOs in a data kit, their relationships and tags are automatically included if they are defined during the packaging process.
To check the deployment status, click Deployment History.
If a component fails during deployment, the process stops, and any subsequent components in the sequence aren’t deployed.
j