txn-data-harness

Generates and verifies Revenue Cloud transaction demo data through staged lifecycle scenarios.

5|3|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/SalesforceLabs/revenue-cloud-foundations --skill txn-data-harness-salesforcelabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: txn-data-harness
Source: https://github.com/SalesforceLabs/revenue-cloud-foundations/tree/main/.cursor/skills/txn-data-harness
Command: npx skills add https://github.com/SalesforceLabs/revenue-cloud-foundations --skill txn-data-harness-salesforcelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Creating realistic Revenue Cloud demo data requires orchestrating a long chain of Salesforce lifecycle steps (Opportunity, Quote, Order, activation, invoicing) with correct API payloads and billing prerequisites. This Skill plans, generates, inspects, continues, verifies, and cleans up that transaction demo data safely using the Transaction Data Harness. ## Core Features & Use Cases - Staged scenario generation: Run quote-to-invoice, direct-order, and invoice-ingestion scenarios from YAML configs with plan/dry-run safety checks before any writes. - Manifest-driven operations: Inspect, continue, and verify partial runs using run manifests, and start the separate usage-upload and rating stages when needed. - Live verification and cleanup guidance: Verify created records in Salesforce via SOQL on manifest ids and clean up deletable records child-to-parent, with clear warnings about non-deletable Posted Invoices and BillingSchedules. - Use Case: A solutions engineer needs a few posted invoices in a demo org. They plan a smoke scenario, run it with concurrency 1 against an sf alias, inspect the manifest, and confirm the invoice status with a SOQL query before scaling up. ## Quick Start Ask the agent to plan and run the 01-smoke-test sales transaction scenario against your sf org alias, then inspect the manifest and verify the created invoice in Salesforce.

Frequently Asked Questions about txn-data-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Revenue Cloud demo transactions in a Salesforce org?

Run the Transaction Data Harness CLI with a YAML scenario config against an sf org alias. Always run the plan command first, then execute a small smoke scenario with concurrency 1, inspect the run manifest, and verify records with SOQL before scaling.

How do I create standalone posted invoices without a quote or order?

Use the invoice_ingestion scenario kind, which posts a Composite Graph payload to the invoicing ingest endpoint. Posted ingestion requires an active non-taxable TaxTreatment in the org, and taxable lines additionally require an active taxable TaxTreatment.

Why did my harness run stop at the order stage?

Runs stop at order_draft when the target account is not billing-ready, because activation creates BillingSchedules and Assets that require billing setup. Inspect the manifest and plan output, then rerun against a billing-ready account.

Can I use a CCI org alias with the Transaction Data Harness?

No, the harness only works with sf CLI aliases passed via the --org flag. Confirm the alias with sf org display before running any plan or write command.

Why doesn't --count 1 limit my smoke run?

The --count flag does not override per-scenario count values in the config; precedence is per-scenario, then CLI, then defaults. To smoke a multi-scenario config, edit the per-scenario count to 1 or comment scenarios out.

What records cannot be cleaned up after a harness run?

Posted Invoices and BillingSchedules are platform-managed and not cleanly deletable. Cleanup should delete other records child-to-parent using manifest ids, and activated orders must be reverted to Draft first.