revenue-cloud-data-model

Documents the Salesforce Revenue Cloud schema of 263 objects across 9 domains.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Salesforce Revenue Cloud (RLM) requires knowing hundreds of objects, fields, and relationships, and release-to-release schema changes silently break queries and data plans. This Skill provides a verified, release-current reference of the full RLM data model so agents and developers write correct SOQL, data plans, and integrations. ## Core Features & Use Cases - Domain-organized schema reference: 263 objects, 4,252 fields, and 674 relationships documented across PCM, Pricing, Rates, Configurator, Transactions, DRO, Usage, Billing, and Approvals domains. - Release delta tracking: Verified 262-to-264 field and picklist changes, including the migration of usage policy bindings to ProductUsageResourcePolicy, with common misconceptions explicitly corrected. - Cross-domain relationship maps: Foreign key maps, the quote-to-cash object lifecycle, and SFDMU data plan load-order dependencies. - Use Case: When writing a SOQL query joining Product2 to usage entitlements, consult the Usage domain file to learn that overage chargeability now resolves through ProductUsageResourcePolicy rather than TransactionUsageEntitlement fields removed in release 264. ## Quick Start Ask the agent to explain how products, pricing, and usage grants relate in Revenue Cloud using the data model skill and its domain reference files.

Frequently Asked Questions about revenue-cloud-data-model

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

FAQPage Schema
How do I find relationships between Revenue Cloud objects?

Read the cross-domain-relationships.md file for foreign key maps between domains, or run scripts/ai/query_erd.py with the relationships or path commands against erd-data.json. Product2 is the central hub referenced by nearly every domain.

What changed in the Revenue Cloud schema in release 264?

Release 264 added 70 fields and removed 8, mostly moving usage policy bindings off TransactionUsageEntitlement and UsageResource onto ProductUsageResourcePolicy. The full verified delta is in scripts/erd/schema_diff/262-vs-264-diff.md.

Does the Revenue Cloud ERD include custom fields?

No, custom fields with the __c suffix are excluded by design so the schema stays platform-pure. To verify a custom field exists, query the org directly with sf sobject describe.

Why does my usage query fail on TransactionUsageEntitlement fields?

Fields like ChargeForOverage, RatingFrequencyPolicyId, and UsageAggregationPolicyId were removed from TransactionUsageEntitlement in release 264. Overage chargeability now resolves through ProductUsageResourcePolicy to UsageOveragePolicy.

What is the difference between PUR, PURP, and PUG in Revenue Cloud?

PUR (ProductUsageResource) binds a product to a usage resource, PURP (ProductUsageResourcePolicy) attaches rating and overage policies to that binding, and PUG (ProductUsageGrant) defines the entitlement grant. Note PUG means ProductUsageGrant, not ProductUsageGroup.