Deploy a Custom Script to Data 360 Sandbox by Using CLI (Beta)

The deployment process packages your Python script, its dependencies, and Data 360 configuration, and then uploads them to Data 360.

The CLI deployment automatically invokes custom code by creating a batch data transform. If you prefer to invoke custom code by creating a batch data transform separately, use the UI deployment method instead. See Deploy a Custom Script to Data 360 Sandbox by Using UI.

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.

DMO-DMO Transform Limitation: If your script performs DMO-DMO transforms (transforms that read from and write to Data Model Objects), the datacustomcode deploy command doesn't work as intended. Use the UI deployment instead. See Deploy a Custom Script to Data 360 Sandbox by Using UI.
Edition Table
Available in: Developer, Enterprise, Performance, and Unlimited Editions. See Data 360 edition availability.
User Permissions Needed
To deploy a custom script and invoke custom code by creating a batch data transform using datacustomcode CLI:Permission set:
  • Data Cloud Architect

  1. Open a terminal in your local environment, and then go to the directory that contains your custom script in your SDK project folder.

  2. If needed, configure the datacustomcode CLI for your Salesforce Data 360 environment.

    Running the datacustomcode configure command is a one-time setup per environment or profile. Rerun this command only if your credentials or environment details change, or if you want to set up a new profile.

  3. Deploy your custom code and invoke it by creating a batch data transform that uses the deployed custom code.

  • --name <DEPLOYMENT_NAME> (Required): Name for your custom code deployment and batch data transform.

  • --cpu-size <CPU_SIZE> (Required): CPU size for the deployment. Default is CPU_XL. Available options are CPU_L(Large), CPU_XL(Extra Large), CPU_2XL(2X Large), and CPU_4XL(4X Large).

  • --path <DIRECTORY>: (Optional) Path to your code directory, which is packaged automatically. Defaults to the current directory (.) if not specified.

  • --description <DESCRIPTION>: (Optional) Description of the batch data transform. Default is "" (empty).

    Example:

  1. Confirm that the code deployment is successful. See Deployment Details.

  2. In the Data 360 UI, go to Data Transforms to verify that the batch data transform is created and custom code is invoked.