deploying-omnistudio-datapacks
PopularSalesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs), sets up DataPack CI/CD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use deploying-metadata), authoring OmniStudio artifacts (use building-omnistudio-*), or writing Apex/LWC business logic (use generating-apex/generating-lwc-components).
Salesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs), sets up DataPack CI/CD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use deploying-metadata), authoring OmniStudio artifacts (use building-omnistudio-*), or writing Apex/LWC business logic (use generating-apex/generating-lwc-components).
deploying-omnistudio-datapacks: Vlocity Build DataPack Deployment
Use this skill when the user needs Vlocity DataPack deployment orchestration: export/deploy workflow, manifest-driven deploys, failure triage, and CI/CD sequencing for OmniStudio/Industries DataPacks.
Scope
Use deploying-omnistudio-datapacks when work involves:
-
vlocity packDeploy,packRetry,packContinue,packExport,packGetDiffs,validateLocalData -
DataPack job-file design (
projectPath,expansionPath,manifest,queries) -
org-to-org DataPack migration and retry loops
-
troubleshooting DataPack dependency, matching-key, and GlobalKey issues
Delegate elsewhere when the user is:
-
deploying standard metadata with
sf project deploy-> deploying-metadata -
building OmniScripts, FlexCards, IPs, or Data Mappers ->
building-omnistudio-* -
designing Product2 EPC bundles -> modeling-omnistudio-epc-catalog
-
writing Apex/LWC code -> generating-apex, generating-lwc-components
