Migrate Custom Code from Sandbox to Production by Using a DevOps Data Kit (Beta)

Use a DevOps data kit to move custom code deployments or batch data transforms created by using custom code from sandbox to production. When you add a batch data transform created using custom code to your data kit, the associated custom code is automatically included in the data kit. When your custom code references either data lake objects or data model objects, you must manually add the referenced objects to the data kit.

Code extension is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Beta Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.
Edition Table
Available in: Developer, Enterprise, Performance, and Unlimited Editions. See Data 360 edition availability.
User Permissions Needed
To migrate custom code deployments, batch data transforms, DLOs, or DMOs from a Data 360 sandbox to production:Permission set:
  • Data Cloud Architect

  1. Access to both sandbox and production Data 360 orgs with appropriate permission sets in both environments.

  2. Validate your custom code deployments and batch data transforms created by using custom code in a sandbox. See Run Custom Code.

  1. In your sandbox org, go to Data Cloud Setup.

  2. Under Developer Tools, click Data Kits.

  3. Click New.

  4. For Data Kit Type, select DevOps.

  5. Name the data kit and add an optional description, such as what it contains.

  6. Save your changes.

  7. Add custom code deployments or batch data transforms or both to your data kit by using one of these options:

    • Option 1: Add Data Transforms

      1. Click Add next to Data Transforms, select the batch data transforms created by using custom code that you want to migrate, and click Save.
      2. When you add a batch data transform, the custom code it references is automatically included in the data kit.
      3. If your custom code 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 Custom Code

      1. Click Add next to Data Custom Codes, select your custom code deployments, and click Save.
      2. If your custom code 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 Custom Code

      1. You can add both batch data transforms and custom code to the same data kit.
      2. Add custom code directly only if it's not already referenced by the batch data transforms you've added.
      3. If your custom code references data lake objects or data model objects, you must manually add the referenced objects to the data kit (see steps 8–9).

  8. If your custom code references data model objects, click Add next to Data Models, select the DMOs that your custom code references, and click Save.

  9. If your custom code references data lake objects, click Add next to Data Lake Objects, select the DLOs that your custom code references, and click Next. Then, click Save.

  1. Review the component list to ensure that all dependencies are included.
  2. Check the publishing sequence to verify components deploy in the correct order: DLOs and DMOs deploy first, followed by custom code deployments, and then batch data transforms created by using custom code that reference them.

    If you add both batch data transforms and custom code to the same data kit, ensure the publishing sequence is correct. Custom code must deploy before any batch data transforms that references it.
  3. Click Publish to make the data kit available for deployment.

For detailed instructions, see Add the Data Kit to a Package.

  1. In your production org, go to Data Cloud Setup and click Data Kits.

  2. Open your data kit, and click Data Kit Deploy.

  3. To deploy the data kit, select a data space, and add the connection org details of the data bundle.

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