---
schema_version: "1"
id: f30345122714a679b785f60eae4d827ea1306b4441ffd4d3d80b665fb0ade64c
title: Quick Start
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-code-ext/guides/quickstart.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/quickstart.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: f9e1b711baa0318dcd5f09ebe403258cd6dda445d5b30e4124f3441f8e3dd9c0
products:
  - Data 360 Code Extension Guide
  - Data 360 Developer Documentation
---
# Quick Start

Set up your sandbox and local environment to run a sample batch data transform script locally against the sandbox. Deploy the script to your sandbox, invoke code extension by creating a batch data transform, and then run the batch data transform to validate the code extension's execution in the sandbox.

The sample script `entrypoint.py` reads data from the `Account_Home__dll` data lake object (DLO), converts the `description__c` column 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.**

| Edition Table                                                                                                                                                                                                 |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Available in: **Developer**, **Enterprise**, **Performance**, and **Unlimited** Editions. See [Data 360 edition availability](https://help.salesforce.com/s/articleView?id=sf.c360_a_dc_editions.htm&type=5). |

| Permission Sets Needed                 |                                                        |
| -------------------------------------- | ------------------------------------------------------ |
| To run the sample script in a sandbox: | Permission set: <ul><li>Data Cloud Architect</li></ul> |

## Step 1: Access a Data 360 Sandbox

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](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox_create.htm&type=5).

## Step 2: Create Data Lake Objects

Create the required data lake objects (DLOs) to match the requirements of the `entrypoint.py` script. See [Create Data Lake Objects](https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/create-dlos.md).

## Step 3: Set Up Salesforce CLI for Code Extension

Install Salesforce CLI and the Code Extension plugin on your computer. Authenticate Salesforce CLI to your Data 360 sandbox, and then initialize a script package. See [Set Up Salesforce CLI for Code Extension](https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/set-up-sdk.md).

**note:** When you authenticate Salesforce CLI to your Data 360 sandbox, specify `myorg` as the alias. In the next steps, every command that requires a target sandbox uses `--target-org myorg`.

## Step 4: Run a Sample Script Locally

1. Go to your code extension package directory.

   ```bash
   cd my_package
   ```

2. Run this sample script against your sandbox.

   ```bash
   sf data-code-extension script run --entrypoint ./payload/entrypoint.py --target-org myorg
   ```

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

## Step 5: Deploy and Invoke the Sample Script

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

   ```bash
   sf data-code-extension script scan --entrypoint ./payload/entrypoint.py
   ```

2. Create a deployment package.

   ```bash
   sf data-code-extension script zip --package-dir ./payload
   ```

3. Deploy the sample code extension to your sandbox.

   ```bash
   sf data-code-extension script deploy --name my_custom_script --package-version 1.0.0 --description "Sample uppercase Account description" --package-dir ./payload --target-org myorg --cpu-size CPU_L
   ```

4. Invoke code extension by creating a batch data transform. See [Invoke Code Extension by Creating a Batch Data Transform](https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/create-batch-transform.md).

5. Verify that the deployment status of `my_custom_script` is successful in the Data 360 UI. See [Monitor Custom Script Deployments and Execution History](https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/view-deployment-details.md).

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

## Step 6: Monitor Code Extension Execution

Check the code extension execution status. See [Check Batch Data Transform Status](http://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_status.htm&type=5). Review the transformed data to verify that it matches your expectations.

If the code extension execution fails, review the Run History tab in your code extension 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](https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/view-deployment-details.md).

## See Also

- [Write and Validate Custom Scripts](https://developer.salesforce.com/docs/data/data-cloud-code-ext/guide/author-custom-script.md)