Quick Start (Beta)

Set up your sandbox and local environment to run a sample batch data transform script locally. Deploy the script to your sandbox, invoke custom code by creating a batch data transform, and then run the custom code by running the batch data transform to validate its execution.

The sample script entrypoint.py reads data from the Account_Home__dll data lake object (DLO), converts the Description__c field to uppercase, drops the KQ_ParentId__c and KQ_Id__c columns (if present), and writes the transformed data to the Account_Home_copy__dll DLO.

Estimated time: ~20 minutes.

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.
Permission Sets Needed
To run the sample script in a sandbox:Permission set:
  • Data Cloud Architect

Make sure that you have access to a sandbox with appropriate permission sets. If you don’t have a sandbox, create one. See Create a Data 360 Sandbox.

Set up an external client app to enable the SDK to authenticate with your sandbox. See Set Up an External Client App for Data Custom Code SDK.

Create the required data lake objects (DLOs) to match the requirements of the entrypoint.py script. See Create Data Lake Objects.

Install the SDK, create the SDK project named my_package, and configure datacustomcode CLI for your Data Cloud environment. See Set Up Data Custom Code SDK.

  1. Go to your SDK project directory.

  2. Run this sample script.

  3. Review the output in your local terminal to verify that the batch data transform is successful and works as expected.

  1. Create a Data 360 configuration file from your sample script.

  2. Deploy the sample script to your sandbox and invoke custom code by creating a batch data transform that uses the deployed script.

The CLI automatically packages (zips) your script and any dependencies found in the payload directory and deploys the package with the deployment name my_custom_script. It then invokes custom code by creating a batch data transform with the same name by using the deployment.

  1. Verify that the deployment status of my_custom_script is successful in the Data 360 UI. See Monitor Custom Script Deployments and Execution History.

  2. To run the my_custom_script batch data transform by using the Data 360 UI, click Data Transforms, click the triangle to the right of my_custom_script, and then select Run Now.

Check the custom code execution status. See Check Batch Data Transform Status. Review the transformed data to verify that it matches your expectations.

If the custom code execution fails, review the Run History tab in your custom code deployment details to see detailed execution logs, error messages, and performance metrics. This information helps you identify the root cause of failures and provides insights for debugging your custom scripts. See Run History.