Salesforce Docs Portal

Deploy Data Kit Components in Data 360

After you create and install a standard data kit in a managed package, you can deploy package components such as data streams, batch data transforms, calculated insights, and data graphs from Data 360 with Package Manager in your target org.

Required Editions

Available in: All Editions supported by Data 360. See Data 360 edition availability.
User Permission Set Needed
To deploy data kit components:

Permission set:

  • Data Cloud Architect

Before you begin, understand the deployment guidelines and limitations.

  • Before you deploy a data kit, verify that every corresponding project, database, dataset, schema, and table has the same name in the source and target environments. A data kit captures these names from the source connection and doesn’t remap them during deployment. If any name differs, deployment fails. For example, deployment fails if a schema is named Sales in the source environment but DevSales in the target environment.
  1. In your org, create and install a managed package with a data kit.
  2. Go to your target org, and use the package URL to install the managed package.
  3. In your target org, under Developer Tools, click Data Kits.
  4. Open your data kit, and click Data Kit Deploy.
  5. To deploy the data kit components, select a data space, and add the connection org details of the data bundle.
  6. 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.

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

To programmatically deploy all the data kit components in the target org, use the Deploy Data Kit Components Connect REST API endpoint.

After you deploy the packaged data stream, your data stream is created and is identical to the one in your package instance. If the data stream in your package was mapped to data models, they’re mapped automatically.

See Also