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).

examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md

View on GitHub
# Deployment Transcript: Business Internet Plus Bundle

This transcript captures the skills used plus the planning and execution process for deploying `business-internet-plus-bundle` with Vlocity Build.

---

## Task Summary

Deploy the `Business Internet Plus` Product2 bundle DataPack and document the end-to-end process in `omnistudio-datapacks-deploy/examples`.

---

## Skills Used

### 1) `omnistudio-datapacks-deploy` (Primary)

**Why used:** The task is DataPack deployment orchestration with Vlocity Build commands (`validateLocalData`, `packDeploy`, `packRetry`) and failure triage.

**Applied guidance:**

- Validate-first execution (`validateLocalData` before deployment).
- Deterministic job file (`projectPath`, `expansionPath`, `manifest`) for reproducible scope.
- Retry loop and failure interpretation.

### 2) `omnistudio-epc-catalog-generate` (Supporting)

**Why used:** The deployment target is an EPC Product2 offer bundle sample with Product Child Item dependencies and companion artifacts.

**Applied guidance:**

- Confirmed Product2 offer markers and companion file consistency.
- Preserved `%vlocity_namespace%` placeholders and stable GlobalKey references.

### 3) `platform-metadata-deploy` (Supporting preflight pattern)

**Why used:** Reused deployment preflight discipline for target org/tooling readiness and concise completion reporting.

---

## Planning Process (Executed)

1. Confirm where the source bundle artifacts were authored.
2. Stage those artifacts into a standard Vlocity expansion path under `vlocity/Product2/<global-key>/`.
3. Build a deterministic deploy job file in this example folder.
4. Run pre-deploy validation (`validateLocalData`).
5. Run actual deployment (`packDeploy`).
6. Run retry (`packRetry`) to confirm whether the failure is transient or dependency-blocking.
7. Capture findings and next safe action.

---

## Execution Details

### A) Staging for deploy

Source payload location:

- `skills/omnistudio-epc-catalog-generate/examples/business-internet-plus-bundle`

Deploy staging location:

- `vlocity/Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101`

Staged files include:

- `Business-Internet-Plus_DataPack.json`
- `Business-Internet-Plus_AttributeAssignments.json`
- `Business-Internet-Plus_ProductChildItems.json`
- `Business-Internet-Plus_PricebookEntries.json`
- `Business-Internet-Plus_PriceListEntries.json`
- `Business-Internet-Plus_ObjectFieldAttributes.json`
- `Business-Internet-Plus_OrchestrationScenarios.json`
- `Business-Internet-Plus_DecompositionRelationships.json`
- `Business-Internet-Plus_CompiledAttributeOverrides.json`
- `Business-Internet-Plus_OverrideDefinitions.json`
- `Business-Internet-Plus_ParentKeys.json`

### B) Job file used

- `skills/omnistudio-datapacks-deploy/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml`

Key settings:

- `projectPath: .`
- `expansionPath: vlocity`
- `manifest: Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101`

### C) Commands executed

```bash
npx --yes vlocity -sfdx.username sample-uat -job "skills/omnistudio-datapacks-deploy/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml" validateLocalData

npx --yes vlocity -sfdx.username sample-uat -job "skills/omnistudio-datapacks-deploy/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml" packDeploy

npx --yes vlocity -sfdx.username sample-uat -job "skills/omnistudio-datapacks-deploy/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml" packRetry
```

### D) Command outcomes

`validateLocalData`:

- Success (`1 Completed`)

`packDeploy`:

- Auto-settings migration phase completed successfully.
- Bundle deploy failed with dependency error:
  - `This DataPack has a reference to another object which was not found -- Product2/21e9dce1-4f89-4f99-a7b2-9cb5d6332101`

`packRetry`:

- Failed with the same missing reference error.

---

## Root Cause

The bundle references child Product2 DataPacks that are not currently present in local expansion scope and/or target org at deploy time.

Missing child Product2 keys confirmed absent from local `vlocity/Product2`:

- `21e9dce1-4f89-4f99-a7b2-9cb5d6332101` (Managed Router)
- `43f2fd94-6114-449b-a1b4-b8dd7238b202` (Internet Security Suite)
- `64a06b24-1135-4f2e-95a1-3a5f5822c303` (Static IP Add-On)

---

## Completion Block

```text
DataPack goal: deploy
Source org: N/A (local staged payload)
Target org: sample-uat
Scope: Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101
Result: failed (dependency missing)
Key findings:
- validateLocalData passed (1 completed)
- packDeploy failed: missing referenced child Product2
- packRetry failed with same error
Next step:
- Stage/deploy the three child Product2 DataPacks first (or include them in manifest), then rerun packDeploy and packRetry.
```
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