--- cuppy_hub: salesforce cuppy_path: reference/official/data360/data-cloud-dev/guide/dc-deploy_data_kit_using_cli.md cuppy_section: docs cuppy_doc: ENRJ-GQWM cuppy_doc_uuid: d616057d-7f52-46bd-a77a-f9e456a8fa5c cuppy_permalink: https://cuppy.io/salesforce/d/ENRJ-GQWM cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-dev/guide/dc-deploy_data_kit_using_cli cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: d09f472c07ca5b94299ea569c3100513f2f29566f7a2232795734eceaa47a071 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Use CLI to Deploy Changes from a Sandbox to Data 360 As a Salesforce developer, you can move your Data 360 metadata and process definitions for Data 360 features between sandbox orgs or between production orgs. To accomplish this, you use a temporary sandbox org that has Data 360 enabled and provisioned. 1. Deploy the data from the production org to the temporary sandbox org. 2. Deploy those changes from the temporary sandbox to a sandbox linked to the new production org. 3. Push the changes from the linked sandbox into the new production org. 4. Add the feature metadata that you want to deploy to a DevOps data kit. 5. After the metadata is in the data kit, retrieve it into a Salesforce DX project manifest. 6. Finally, you can deploy the metadata to the production org. When you deploy changes from a sandbox, you can deploy them back to the production org or to another sandbox. This process involves multiple steps in both Data 360 and the Salesforce Platform. Bookmark this page or keep it open in a separate window to refer to this topic. For simplicity, this topic uses the term “production,” which can refer to the production org from which the sandbox was created. | User Permission Set Needed | | | --- | --- | | To deploy data kit components: | Permission set: Data Cloud Architect | Make sure to complete these prerequisites before you create and start working on a Salesforce DX project. * Create a deployment connection between the production org and the sandbox org. See [Authorize a Deployment Connection](https://help.salesforce.com/s/articleView?id=t_changesets_deployment_connection.htm). * Install VS Code. See [Install Salesforce Extensions Visual Studio Code](https://developer.salesforce.com/tools/vscode/en/vscode-desktop/install#visual-studio-code). * Install the Salesforce CLI. See [Install Salesforce CLI](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm). * Install the Salesforce Extension Pack (Expanded) for VS Code. See [Salesforce Extension Pack (Expanded)](https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-expanded). 1. Open the VS Code editor and from VS Code Command Palette, run `SFDX: Create Project with Manifest`. See [Create Project](https://developer.salesforce.com/docs/platform/sfvscode-extensions/guide/create-project.html). 2. In the `sfdx-project.json` file, specify the login URL for the production org, which is [https://login.salesforce.com](https://login.salesforce.com/). 3. In the `sfdx-project.json` file, specify the login URL for the sandbox org, which is [https://test.salesforce.com](https://test.salesforce.com/). ![Image 1: Salesforce DX project JSON file for DevOps data kit](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/DataKit_Project_JSON.png) 1. Authorize the sandbox org and the production org to work with your Salesforce DX project. See [Authorize your Production Org](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_prod_org.htm). 1. Go to Data Cloud Setup and create a data space in the sandbox org and the production org. See [Create a Data Space](https://help.salesforce.com/s/articleView?id=data.c360_a_data_stream_bundle_package_kits.htm). > **Note:** In Data Cloud Setup, make sure that the data space with the same prefix name exists in both the sandbox org and the production org. 1. In your sandbox org, go to Data Cloud Setup and create a data kit. See [Create a Data Kit](https://help.salesforce.com/s/articleView?id=data.c360_a_data_stream_bundle_package_kits.htm). 2. For Data Kit Type, select **DevOps**. 3. Add Data 360 components that you want to deploy from the DevOps data kit and review the publishing sequence for these components. The components that you can add include data streams, data lake objects, calculated insights, and data graphs. See [Data 360 in a Sandbox](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox.htm). 1. In your sandbox org, under Developer Tools, click **Data Kits**. 2. Select the DevOps data kit, and then click **Download Manifest**. To download the manifest file programmatically, use the [get data kit manifest](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Data-Kits/paths/~1ssot~1datakit~1%7BdataKitDevName%7D~1manifest/get) Connect REST API endpoint. The `package.xml` file that you downloaded contains all the metadata components related to the DevOps data kit. Use this `package.xml` file in your Salesforce DX project to retrieve the data kit metadata. Sample `package.xml` file for a data kit. 1. To retrieve the DevOps data kit metadata into the sandbox org, run the `sf project retrieve start --manifest manifest/package.xml` command. After this command completes, you see new project folders that contain the data kit metadata. Consider uploading the entire project to GitHub or any other source control system. This practice helps with version control, collaboration, and ensures that your project is backed up and accessible to your team. 2. > **Important:** > Don’t skip this step Unix users, execute these commands to delete any key qualifier files related to the project. If you’re a Windows user, search for key qualifier files in your project directory. Manually delete those files and their references from the project. ![Image 2: Use Key Qualifier tag to remove files](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/DataCloud_DataKit_KQ_file.png) 1. To start the deployment, run: `sf project deploy start --manifest package.xml.` See [project deploy start](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_project_commands_unified.htm). 2. To check the deployment status, click **Deployment History**. After the data kit deploys in the production org, you can see the data kit, including all of its data stream bundles, data models, and calculated insights. The metadata and process definitions from your sandbox org data kit are deployed in your production org. Review this information to resolve any deployment failures. **Missing FieldSrcTrgtRelationship Reference for DMO Relationship** This error occurs during deployment when you try to deploy data model objects (DMOs) that have relationships defined, but the required `FieldSrcTrgtRelationship` metadata, which links the source and target fields of these relationships, is either missing or contains invalid references. Locate all XML files mentioned in the error within your SFDX project and manually delete those XML files. Then reattempt the deployment. **Missing FieldSrcTrgtRelationship Metadata** This error occurs when your deployment fails because a required `FieldSrcTrgtRelationship` definition can’t be found. To fix this, you must retrieve the missing `FieldSrcTrgtRelationship` files from your source org. Here are two ways that you can do it: **Option 1: Retrieve specific relationships by using org browser** 1. In your Salesforce DX project, open the org browser. 2. Go to the Field Source Target Relationships folder. 3. Find and retrieve only the specific relationship files mentioned in the error message. ![Image 3: Retrieve relationship files](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/DataCloud_DataKit_Lookup.png) **Option 2: Retrieve relationships by using package.xml manifest file** 1. In your terminal, run the `sf project retrieve start --manifest manifest/package.xml` command to retrieve metadata. 2. Open your `package.xml` file and add the missing `FieldSrcTrgtRelationship` names within the tag for `FieldSrcTrgtRelationship`. Example: 1. If your project includes any key qualifier files related to these DMOs or relationships, make sure to delete them. [](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/dc-deploy_data_kit_using_cli.html)[Refer to Step 6](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/dc-deploy_data_kit_using_cli.html#6-retrieve-the-devops-data-kit-metadata) 2. Now, you can reattempt the deployment of your data kit to your target org. **Unable to Deploy Data Lake Object (DLO) Schema Changes** This error occurs during data kit deployment when the target org contains fields that are missing from the source org’s DLO. To resolve this problem, synchronize schemas between the source and target orgs before deploying. > **Note:** Keep sandbox and production schemas synchronized before data kit deployments to prevent schema mismatch errors. **Inactive Connectors After Deployment** This error occurs when your deployment completes, but some of the deployed connectors are in an inactive state in the target (production) org. While connection configurations are replicated, the sensitive authorization data is not copied during a sandbox refresh or certain deployment types. To resolve inactive connector issues, you must re-authorize them in the target (production) org. 1. In your production org, go to Data Cloud and click **Connectors**. 2. Identify connectors that show an Inactive status. 3. Reauthorize the inactive connectors. 4. Redeploy the data kit to ensure that all components are correctly linked and operational. * * * * _Salesforce Help_: [Install and Configure DevOps Center](https://help.salesforce.com/s/articleView?id=platform.devops_center_setup.htm) * _Salesforce Help_: [Data 360 in a Sandbox](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox.htm) * _Salesforce Help_: [Deploy Data 360 Changes from a Sandbox](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox_deploy.htm) * _Data 360 Connect REST API_: [Get data kit manifest](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Data-Kits/paths/~1ssot~1datakit~1%7BdataKitDevName%7D~1manifest/get) * _Data 360 Connect REST API_: [Deploy data kit components](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Data-Kits/paths/~1ssot~1data-kits~1%7BdataKitDevName%7D/post) * _Salesforce Help_: [Data Services Billable Usage Types for Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_usage_types.htm&type=5) * _Salesforce Help_: [Billing Considerations for Data 360 Sandbox](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox_billing_considerations.htm&type=5) --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.