Agent skill · forcedotcom
consumer-goods-rtr-datacloud-export-configure
Configure a Trade Promotion Management (TPM) org's RTR (Real Time Reporting) export pipeline to push promotion measures into Data Cloud (Data 360) for Trade Promotion Effectiveness (TPE) dashboards. Use when a customer or admin wants to set up the RTR export for Data Cloud measures, configure the RTR report for TPE, or as a delegated step from consumer-goods-tpe-dashboard-configure.
What it needs
About 5k tokens when loaded.
What this skill does
Setup RTR Data Cloud Export Configures the Data-Cloud-targeted RTR exports: the DataCloudEnabled system setting, a scoped SF Data Sync, an RTRReportConfigurationc record (with its KPISetc) for Data Cloud export, and the export trigger/status/abort REST calls. Standalone and self-contained — runs on its own, or as a delegated step invoked by consumer-goods-tpe-dashboard-configure, which passes through its own already-collected username, dry-run flag, and GenieAdmin confirmation result. Distinct from a sibling CSV-export RTR skill (if present in this org's checkout): that skill targets Usagec IN ('integrationmeta','reportmeta') for CSV export to the CGCloud Processing Services host. This skill targets Data Cloud export. Same underlying RTRReportConfigurationc object and KPISetc Apex patterns, different Usagec values and JSONc shape — this skill does not invoke or depend on that sibling. For now, this skill only supports Usagec = 'datacloudpromotionmeasuresmeta' (JSONc.object = "promotionmeasures") — it is hardcoded, never asked as an input. datacloudaccountplanmeasuresmeta (account-plan measures) is not yet wired up. Inputs and namespace detection Read references/inputs-and-namespace.md before starting. It covers: The username/dry-run/GenieAdmin/TPM-Admin/namespace inputs that must be collected (or passed through by a calling skill) before Phase 1. The Sales Org / KPI Set / measure-codes / date-from inputs that Phase 6 collects lazily, per Sales Org, only once its existing-config check comes back empty. The namespace-detection procedure (scripts/detect-namespace.js) and the four NS/NSSEGMENT/NSAPEX/NSFIELD derivations used throughout every phase below. scripts/render-apex.js (Apex template rendering) and scripts/resolve-id-by-name.js (name-to-id lookups) both load scripts/soql-escape.js to escape substituted/queried literals for safe SOQL/Apex interpolation. Phases Full step-by-step commands, queries, and Apex templates for every phase are in references/procedure.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/consumer-goods-rtr-datacloud-export-configure