Skip to content

forcedotcom/sf-skills / skills/omnistudio-datapacks-deploy

omnistudio-datapacks-deploy

Verified

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 platform-metadata-deploy), authoring OmniStudio artifacts (use omnistudio-*-build), or writing Apex/LWC business logic (use platform-apex-generate/experience-lwc-generate).

# omnistudio-datapacks-deploy

Salesforce Industries DataPack deployment automation using Vlocity Build. Export, validate, deploy, retry, and compare OmniStudio/Vlocity DataPacks with predictable workflow guardrails.

## Features

- **DataPack Deployment Workflow**: Run `packExport`, `packDeploy`, `packRetry`, `packContinue`, and `packGetDiffs`
- **Job File Guidance**: Build deterministic `projectPath`, `expansionPath`, `queries`, and `manifest` job patterns
- **Validation-First Operations**: Gate deployment with `validateLocalData` and dependency checks
- **Failure Triage**: Diagnose matching-key, GlobalKey, dependency, and configuration drift failures
- **CI/CD Patterns**: Support manifest-driven and git-aware deployment sequencing

## Usage

Invoke this skill when working with OmniStudio/Vlocity DataPack deployments:

```text
Skill: omnistudio-datapacks-deploy
Request: "Deploy my OmniStudio DataPacks to UAT using Vlocity Build and include retry guidance."
```

## Common Operations

| Operation | Example Request |
|-----------|-----------------|
| Export | "Export DataPacks from source org with this job file." |
| Validate local files | "Run pre-deploy validation and identify key issues." |
| Deploy | "Deploy DataPacks to target org using packDeploy." |
| Retry failures | "Run packRetry and summarize what remains." |
| Resume interrupted run | "Continue the failed deployment job." |
| Compare with target | "Run packGetDiffs and report drift." |

## Key Commands

```bash
# Validate local DataPack integrity
vlocity -sfdx.username [sourceAlias] -job [jobFile].yaml validateLocalData

# Export from source
vlocity -sfdx.username [sourceAlias] -job [jobFile].yaml packExport

# Deploy to target
vlocity -sfdx.username [targetAlias] -job [jobFile].yaml packDeploy

# Retry failed DataPacks
vlocity -sfdx.username [targetAlias] -job [jobFile].yaml packRetry

# Continue interrupted execution
vlocity -sfdx.username [targetAlias] -job [jobFile].yaml packContinue

# Compare local files to target org
vlocity -sfdx.username [targetAlias] -job [jobFile].yaml packGetDiffs
```

## Best Practices

| Rule | Details |
|------|---------|
| Validate first | Run `validateLocalData` before deploy |
| Keep scope minimal | Prefer manifest/key-scoped deploys for safer rollouts |
| Retry intentionally | Use `packRetry` while error count is decreasing |
| Preserve key strategy | Keep matching keys and GlobalKeys consistent across orgs |
| Compare post-deploy | Run `packGetDiffs` to verify target parity |

## Cross-Skill Integration

| Related Skill | When to Use |
|---------------|-------------|
| platform-metadata-deploy | Deploy non-DataPack Salesforce metadata with `sf project deploy` |
| omnistudio-omniscript-generate | Author OmniScripts before deployment |
| omnistudio-flexcard-generate | Build FlexCards before deployment |
| omnistudio-integration-procedure-generate | Build Integration Procedures before deployment |
| platform-apex-logs-debug | Investigate runtime/triggers/log failures surfaced during deploy |

## Documentation

- [SKILL.md](SKILL.md) - Full DataPack deployment workflow and operating rules
- [references/job-file-template.md](references/job-file-template.md) - Baseline job file patterns
- [references/troubleshooting-matrix.md](references/troubleshooting-matrix.md) - Common failures and fix directions
- [examples/business-internet-plus-bundle/TRANSCRIPT.md](examples/business-internet-plus-bundle/TRANSCRIPT.md) - Validation planning/execution transcript and outcomes
- [examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md](examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md) - Deployment execution transcript with packDeploy/packRetry results

## Requirements

- Node.js 18+
- Vlocity Build CLI (`npm install --global vlocity`)
- Salesforce CLI v2 (for org auth and context)
- Source and target org access
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall