deploying-omnistudio-datapacks

Sequence Vlocity Build DataPack commands for export-to-target deployment workflows.

803|289|Updated Nov 7, 2025

Search Tags:#omnistudio #vlocity build #datapack deployment #validate local data #packretry #globalkey #manifest driven

Ready to run

npx skills add https://github.com/forcedotcom/sf-skills --skill deploying-omnistudio-datapacks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploying-omnistudio-datapacks
Source: https://github.com/forcedotcom/sf-skills/tree/main/skills/deploying-omnistudio-datapacks
Command: npx skills add https://github.com/forcedotcom/sf-skills --skill deploying-omnistudio-datapacks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents slow, error-prone OmniStudio/Vlocity DataPack deployments by guiding an export/validate/deploy/retry workflow that handles common dependency and configuration drift failures.

Core Features & Use Cases

Vlocity Build DataPack orchestration: Execute validateLocalData, packExport, packDeploy, packRetry, packContinue, and packGetDiffs in the right order.
Job-file driven, deterministic scope: Help users structure projectPath, expansionPath, queries, and manifest patterns to keep deployments predictable.
Failure triage and safe recovery loops: Diagnose matching-key, GlobalKey, missing dependency, and “No Configuration Found” issues, then choose the next safest action.
CI/CD-ready deployment patterns: Use manifest-driven sequencing, optional git-aware checks, and a retry loop until errors plateau.

Quick Start

Tell the AI: "I need to validate and deploy my OmniStudio DataPacks to a target org using Vlocity Build with a manifest-scoped job file, and if it fails, give me precise packRetry next steps."

Frequently Asked Questions about deploying-omnistudio-datapacks

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

FAQPage Schema

How do I deploy OmniStudio DataPacks using Vlocity Build without hitting dependency errors?▼

OmniStudio DataPack deployment requires sequencing validateLocalData, packDeploy, and packRetry in a Vlocity Build job file configured with projectPath, expansionPath, and manifest entries to prevent dependency and configuration drift failures.

What is the correct Vlocity Build workflow for exporting and validating local OmniStudio data?▼

The Vlocity Build workflow uses packExport to retrieve data into your projectPath, then runs validateLocalData to check integrity and dependencies before initiating a target org deployment.

How can I troubleshoot GlobalKey and matching-key failures during OmniStudio DataPack migration?▼

Use packRetry and packGetDiffs after a failed packDeploy to diagnose matching-key, GlobalKey, and missing dependency issues, then apply packContinue to safely resume the OmniStudio DataPack migration workflow.

Can I use manifest-driven deployments to set up CI/CD pipelines for OmniStudio DataPacks?▼

Manifest-driven OmniStudio DataPack deployments support CI/CD pipelines by defining deterministic scopes in a Vlocity Build job file, enabling optional git-aware checks and automated retry loops until deployment errors plateau.

Why does my OmniStudio DataPack deployment fail with No Configuration Found errors?▼

No Configuration Found errors during OmniStudio DataPack deployment indicate missing manifest entries or GlobalKey configuration drift; run validateLocalData and packRetry loops to triage dependencies and safely recover the deployment.

Do I need a specific job file structure to run packDeploy and packRetry for Vlocity Build?▼

Vlocity Build packDeploy and packRetry require a job file specifying projectPath, expansionPath, and manifest or queries patterns, along with correct org aliases and preflight guardrails to maintain deterministic deployment scoping.