Consumer Goods Tpe Dashboard Configure
End-to-end headless setup of Trade Promotion Effectiveness (TPE) dashboards for a Trade...
Install
npx skills add forcedotcom/sf-skills --skill consumer-goods-tpe-dashboard-configure -g -a claude-code -y- Repository
- forcedotcom/sf-skills1.1k
- Category
- Business
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Lightabout 1,191 tokens
- Runs scripts
- Yes, review before use
What it does
End-to-end headless setup of Trade Promotion Effectiveness (TPE) dashboards for a Trade Promotion Management (TPM) Cloud org, covering tenant pairing checks, permission sets, SSOT and Tableau Next enablement, C360 SDM verification, the TPM Accruals data kit install, business-period export, RTR Data Cloud export configuration, the TPM_PROMOTION_MEASURE Data Transform, TPE Analytics app install, and optional KPI dashboard customization. Use when a customer or admin wants to set up TPE dashboards, enable Trade Promotion Effectiveness, install the TPE analytics app, or set up and customize TPE dashboards with their own KPIs.
Consumer Goods TPE Dashboard Configure
Bring a TPM org from bare state to a running TPE dashboard in one guided session, driven entirely by sf CLI + REST/anonymous-Apex against an already-authenticated org, never a password or interactive login on the user's behalf.
Persona: a Salesforce TPM System Admin setting up TPE dashboards for their org.
Delegates three of its twelve steps to standalone sibling skills (own SKILL.md, own inputs, self-contained per this repo's skills architecture rules, no shared files):
- Step 7 →
consumer-goods-tpe-datakit-deploy - Step 9 →
consumer-goods-rtr-datacloud-export-configure - Step 12 →
consumer-goods-tpe-dashboard-custom-kpi-configure(optional, only if the customer wants custom KPIs on the base dashboards)
Every other step runs directly in this skill.
Inputs to collect first
Ask before starting. Do not guess.
- TPM System Admin username, must already be authenticated via
sfCLI. Verify withnode ./scripts/sf-rest.js org-status --target-org <username>(neversf org display --jsondirectly, seereferences/phases-1-6.md). - Dry-run?, offer by default. In dry-run, every read/verify/check step still runs; every write/trigger/install step is skipped and recorded as
pending, not run (dry-run).
Also detect the installed package namespace and version-gate the org (Consumer Goods Cloud >= 262.2 required) before Phase 1, see "Namespace detection" in references/phases-1-6.md.
