Data Kit membership

Last updated: October 28, 2026, 17:17 (UTC+1).

Runtime verified

Verification scope: Live-org reads and the explicitly described bounded operations were tested. The operation-specific limitations still apply; this badge does not verify untested writes or general CRUD support.

Back to Data Cloud with Salesforce CLI. Start with its setup, placeholders and safety guidance before running these examples.

Data Kit membership — DataPackageKitObject.

Supplied workflows for Data Kit membership
Retrieve	Create	Update	Delete
Yes	Partial	?	?

Yes: a usable scoped workflow is supplied. Partial: a usable bounded, combined or incomplete asynchronous workflow is supplied. Neither means universal capability. No: proven unavailable in an explicit scope. ?: unknown, untested or no usable workflow supplied. Neither No nor ? displays method icons. means dedicated CLI commands; means API-led requests or facades, even when invoked through the CLI. Two icons identify alternatives, not equivalent coverage. Read each operation's prerequisites and limits. An available operation tab may explain an illustrative mechanism without supplying a usable summary workflow.

Retrieve

CLI — Available: Combined metadata transport only; retrieval does not install the kit.
API — Unknown: No separate API retrieval workflow is supplied.
sf-plugin-data — Unknown: Not implemented in this guide; no workflow is supplied.

CLI

A membership file links a kit definition to a template. Use exact member names from the org; they are not necessarily the kit’s display name.

For the verified combined transport, the integration supplies manifest/package.xml with the actual member names. Here is a small example of that generated file:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
  <types>
    <members>CustomerGraph</members>
    <name>DataKitObjectTemplate</name>
  </types>
  <types>
    <members>CustomerKit</members>
    <name>DataPackageKitDefinition</name>
  </types>
  <types>
    <members>CustomerKitGraphMember</members>
    <name>DataPackageKitObject</name>
  </types>
  <version>65.0</version>
</Package>

With that file supplied, retrieve the pieces together:

sf project retrieve start --manifest manifest/package.xml --target-org SOURCE_ALIAS --api-version 65.0 --wait 10 --json

{ "status": 0, "result": { "success": true, "files": [
  { "fullName": "CustomerGraph", "type": "DataKitObjectTemplate", "state": "Created" },
  { "fullName": "CustomerKit", "type": "DataPackageKitDefinition", "state": "Created" },
  { "fullName": "CustomerKitGraphMember", "type": "DataPackageKitObject", "state": "Created" }
] } }

The member file is force-app/main/default/DataPackageKitObjects/CustomerKitGraphMember.DataPackageKitObject-meta.xml. Capitalization matters. Further members each have their own file in that same directory.

<DataPackageKitObject xmlns="http://soap.sforce.com/2006/04/metadata">
  <masterLabel>Customer Kit</masterLabel>
  <parentDataPackageKitDefinitionName>CustomerKit</parentDataPackageKitDefinitionName>
  <referenceObjectName>CustomerGraph</referenceObjectName>
  <referenceObjectType>DataKitObjectTemplate</referenceObjectType>
</DataPackageKitObject>

Preserve the exact references. For a larger snapshot, the generated manifest includes the other actual template and membership names too. Retrieval does not install the kit, and these links alone do not prove that its components are portable.

Create

CLI — Available: Use the linked joint source-org workflow; independent member creation remains unverified.
API — Unknown: No separate API creation workflow is supplied.
sf-plugin-data — Unknown: Not implemented in this guide; no workflow is supplied.

CLI

The owned Identity Resolution membership link was created together with its definition and template using the shared kit definition example. Independent member creation and portability remain unverified.

Update

Member updates have not been verified.

CLI — Unknown: Member updates have not been verified; no workflow is supplied.
API — Unknown: No API member-update workflow is supplied.
sf-plugin-data — Unknown: Not implemented in this guide; no workflow is supplied.

Delete

CLI — Available: Use the linked joint metadata-deletion workflow; independent member deletion and runtime undeployment remain unverified.
API — Unknown: No separate API deletion workflow is supplied.
sf-plugin-data — Unknown: Not implemented in this guide; no workflow is supplied.

CLI

The owned Identity Resolution membership link was deleted together with its definition and template using the shared kit definition example. Independent deletion of arbitrary member links and runtime component undeployment remain unverified.

Moving a kit is not installing it

Downloading or deploying kit XML only transports its metadata. Instantiation is a separate asynchronous Connect deployment: wait for that job’s final success or error before assuming any runtime component exists.

In particular, an Identity Resolution template can be stored successfully while its later instantiation fails. That does not mean every valid Salesforce-generated kit fails. The available tools do not expose canonical kit creation, component-add or template-generation, so no generated-kit workflow is supplied here. Do not invent template tokens or treat reading a manifest as generating one. Successful canonical kit instantiation and cross-org replay remain unverified; the direct runtime routes above do not require a GUI detour.

For the official workflows, see CLI kit transport and Connect kit deployment.

These examples use vanilla Salesforce CLI commands to call the indicated Metadata or REST API. A missing dedicated CLI command does not mean the underlying API operation is unavailable.