omnistudio-datapacks-deploy

Automates OmniStudio DataPack export, validation, deployment, and retry workflows using Vlocity Build.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill omnistudio-datapacks-deploy-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omnistudio-datapacks-deploy
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/omnistudio-datapacks-deploy
Command: npx skills add https://github.com/padjei/SF_Build --skill omnistudio-datapacks-deploy-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vlocity, and includes references (resource) components.

What problem does it solve? Deploying Salesforce Industries (OmniStudio/Vlocity) DataPacks across orgs is error-prone: missing dependencies, duplicate GlobalKeys, and interrupted jobs cause failed migrations that are hard to diagnose. This Skill provides a structured Vlocity Build workflow with validation gates, retry loops, and failure triage so DataPack deployments become predictable and repeatable. ## Core Features & Use Cases - Full DataPack Lifecycle: Orchestrates packExport, packDeploy, packRetry, packContinue, packGetDiffs, and validateLocalData with a validate-first quality gate. - Job File Design: Guides deterministic job files with projectPath, expansionPath, queries, manifest, and gitCheck options for scoped, CI/CD-friendly deployments. - Failure Triage: Diagnoses common errors such as missing dependency references, duplicate GlobalKeys, and outdated DataPack settings, with a documented troubleshooting matrix. - Use Case: You need to migrate a Product2 EPC bundle from a source org to UAT. The Skill stages the payload, validates local data, deploys with a manifest-scoped job file, retries failures, and reports remaining dependency gaps. ## Quick Start Ask the assistant to deploy your OmniStudio DataPacks to a target org using Vlocity Build with a manifest-scoped job file, including pre-deploy validation and retry guidance.

Frequently Asked Questions about omnistudio-datapacks-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy OmniStudio DataPacks with Vlocity Build?▼

Run vlocity with -sfdx.username pointing to your target org alias and a -job YAML file, then execute packDeploy. Validate first with validateLocalData, and use packRetry afterward to resolve transient failures.

How to retry failed Vlocity DataPack deployments?▼

Run packRetry with the same job file and target org alias. Repeat while the error count decreases; stop when retries plateau and fix the root data or dependency issue before trying again.

Why does packDeploy fail with 'No match found' errors?▼

This error means a referenced DataPack dependency is missing from the target org or local expansion folder. Deploy the missing referenced DataPack key first, then rerun packDeploy or packRetry.

Can I deploy only specific DataPacks instead of the full project?▼

Yes, use the manifest section in the job file to list specific keys like Product2/<global-key>, or pass individual keys. This creates deterministic, scope-limited deployments that are safer for targeted rollouts.

When should I use sf project deploy instead of Vlocity Build?▼

Use sf project deploy for standard Salesforce metadata via Metadata API. Vlocity Build is required for OmniStudio/Vlocity DataPacks such as OmniScripts, FlexCards, Integration Procedures, and Product2 EPC bundles.