Quick Start
Set Up Salesforce CLI for Custom Functions
Monitor Custom Function Deployments
Use a Custom Chunking Function in a Search Index
Verify Custom Chunking Results
Migrate Custom Function to Production
Salesforce CLI, the code extension plugin, and the Data Custom Code Python SDK work together as your local toolchain for Code Extension. Use this setup to develop and test custom chunking functions locally against a sandbox and then deploy them to Data 360 for execution.
| Edition Table |
|---|
| Available in: Developer, Enterprise, Performance, and Unlimited Editions. See Data 360 edition availability. |
| User Permissions Needed | |
|---|---|
| To set up and use the Salesforce CLI for custom function development: | Permission set:
|
Install Salesforce CLI version 2.130.9 or later. See Install Salesforce CLI.
Confirm that your Salesforce CLI version is 2.130.9 or later:
1sf versionIf you have an earlier version, update Salesforce CLI. See Update Salesforce CLI, and then run sf version to confirm.
On Windows, install Node.js LTS and verify the installation.
1node --version
2npm --versionInstall the code extension plugin.
1sf plugins install @salesforce/plugin-data-code-extensionMake sure the installed code extension plugin version is 0.1.5 or later. If you have an earlier version, update the plugin to the latest available version.
1sf plugins
2sf plugins updateInstall the Data Custom Code Python SDK.
macOS and Linux
1python3.11 -m pip install salesforce-data-customcodeWindows
1py -3.11 -m pip install salesforce-data-customcode(Optional) Upgrade the Data Custom Code Python SDK to the latest available version.
macOS and Linux
1python3.11 -m pip install --upgrade salesforce-data-customcodeWindows
1py -3.11 -m pip install --upgrade salesforce-data-customcodeConfirm the SDK installation.
python3.11 -m pip show salesforce-data-customcodepy -3.11 -m pip show salesforce-data-customcodeLog in to your org. From a terminal, run one of the commands with the flags for your org type. Salesforce CLI opens your default browser for Salesforce sign-in. After you sign in, the CLI saves the session on your computer.
Production or Developer Edition
1sf org login web --alias <myorg>Sandbox
1sf org login web --alias <mysandbox> --instance-url https://test.salesforce.comCustom domain
1sf org login web --alias <myorg> --instance-url https://mycompany.my.salesforce.comAfter you sign in, confirm which orgs the CLI is connected to and which alias you must use for code extension commands.
1sf org list
2sf org display --target-org <myorg>For example, run sf org display --target-org myorg to display the connection status of your org alias myorg.
Running the sf org login 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.
Note
Create a code extension function package.
1sf data-code-extension function init --package-dir <PACKAGE_DIR>Example:
1sf data-code-extension function init --package-dir <my_package>Replace <my_package> with the directory name for your project, for example, my_function_package.
The command sets up the directory structure, configuration files, and dependencies for writing, testing, and deploying a custom chunking function.
1```text
2my_package/
3├── requirements.txt
4├── requirements-dev.txt
5├── Dockerfile.dependencies
6├── build_native_dependencies.sh
7├── payload/
8│ ├── config.json
9│ └── entrypoint.py
10├── .datacustomcode_proj/
11│ └── sdk_config.json
12├── .devcontainer/
13│ └── devcontainer.json
14└── README.md
15```Here’s a summary of the directories and files in the package.
| Directory or File | Description |
|---|---|
Dockerfile.dependencies | Used to build dependency layers for packaging workflows. |
build_native_dependencies.sh | Helper script to build native Python dependencies when needed. |
requirements.txt | Lists the Python packages your function needs for deployment. |
requirements-dev.txt | Python packages for local development and testing only. Don’t modify this file. |
payload/ | Contains the function and configuration that the CLI deploys to Data 360. |
payload/config.json | The configuration manifest for a Data 360 code extension package. It defines how the function will be executed and what resources it needs. |
payload/entrypoint.py | Main Python file where you implement your chunking function, for example, function(request, runtime). |
.datacustomcode_proj/sdk_config.json | Project metadata generated by the CLI, for example, type: "function". |
.devcontainer/devcontainer.json | Visual Studio Code Dev Container configuration for a consistent local environment. |
README.md | Package overview, setup notes, and how to run samples in a container or locally. |