
Consumer Goods Tpe Dashboard Custom Kpi Configure
Customize the Trade Promotion Effectiveness (TPE) Analytics dashboards' generic KPI...
Install
npx skills add forcedotcom/sf-skills --skill consumer-goods-tpe-dashboard-custom-kpi-configure -g -a claude-code -y- Repository
- forcedotcom/sf-skills1.1k
- Category
- Engineering
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,185 tokens
- Runs scripts
- Yes, review before use
What it does
Customize the Trade Promotion Effectiveness (TPE) Analytics dashboards' generic KPI slots (Promotion Measure 1-3, Tactic Measure 1-2) with customer-chosen KPI measure codes and display names, without touching the shipped base model. Use when a customer/admin wants to \"customize TPE dashboards\", \"change the KPIs on the Promotion/Tactic Analysis dashboard\", or \"swap in our own measure codes on the TPE dashboard\".
Customize TPE Dashboard KPIs
Headlessly clones the base TPE Analytics semantic-model parameters, visualizations, and dashboards
under a customer-chosen suffix, so a customer's own KPI measure codes appear on the Promotion/Tactic
Analysis dashboards without ever mutating the shipped base model. Driven entirely by sf CLI +
REST against an already-authenticated org. Requires consumer-goods-tpe-dashboard-configure to
have already installed the TPE Analytics app and the Extended TPM Analytics SDM, this skill never
installs those, only customizes on top of them.
Persona: a Salesforce TPM System Admin customizing TPE dashboards for their org's own KPIs.
There is no native "clone" endpoint for any of the three artifact types this skill touches (semantic-model parameters, visualizations, dashboards), every clone is the same three-step pattern: GET the base artifact, deep-copy its JSON and apply overrides, POST the copy as a new artifact. Base-model artifacts are never mutated in place.
The 5 KPI slots, two artifacts per slot, not one
The shipped Extended TPM Analytics SDM exposes 5 generic List-type parameters that the standard
dashboards bind to: Promotion Measure 1-3 (Promotion_Measure_{1,2,3}_prm / _value) and Tactic
Measure 1-2 (Tactic_Measure_{1,2}_prm / _clc). Never assume Tactic mirrors Promotion's
_value naming, resolve both slots' measurement apiNames from the live model per slot, never by
pattern. See references/payload-shapes.md for the confirmed apiNames and JSON shapes.
