revenue-cloud-data-model

Query and reference the Revenue Cloud platform schema across 9 domains and 263 objects.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill revenue-cloud-data-model-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: revenue-cloud-data-model
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/revenue-cloud-data-model
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill revenue-cloud-data-model-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Salesforce Revenue Cloud (RLM) requires knowing which of its 263 platform objects, 4,252 fields, and 674 relationships to use, and release-to-release schema changes (like the 262 to 264 delta) silently break queries and integrations built on outdated assumptions. ## Core Features & Use Cases - Schema Lookup: Query object fields, relationships, and domain membership on demand with the query_erd.py script, including relationship paths between any two objects. - Per-Domain References: Load detailed field and relationship documentation for PCM, Pricing, Rates, Configurator, Transactions, DRO, Usage, Billing, and Approvals domains. - Release Delta Tracking: Review verified 260 to 262 and 262 to 264 schema diffs, including removed fields and their replacement binding sites such as ProductUsageResourcePolicy. - Use Case: When writing a SOQL query to resolve overage chargeability for a usage entitlement, use this Skill to learn that TransactionUsageEntitlement.ChargeForOverage was removed in 264 and the value now comes from UsageOveragePolicy via ProductUsageResourcePolicy. ## Quick Start Ask the agent to explain how products, pricing, and usage grants relate in Revenue Cloud, citing the domain reference files it uses.

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?▼

Run python scripts/ai/query_erd.py with the relationships or path commands against the canonical erd-data.json schema. Cross-domain foreign keys are also documented in cross-domain-relationships.md, organized around hub objects like Product2, Account, and LegalEntity.

What changed in the Revenue Cloud schema between release 262 and 264?▼

Release 264 added 70 fields and removed 8, with 7 of the 8 removals moving usage policy bindings onto ProductUsageResourcePolicy. The full verified delta, including SFDMU plan impact analysis, is in scripts/erd/schema_diff/262-vs-264-diff.md.

Does the Revenue Cloud ERD include custom fields?▼

No, the ERD covers canonical platform schema only and excludes all __c fields by design, including project-deployed RLM_*__c and managed-package fields. To verify a custom field exists, query the org directly with sf sobject describe.

Why does my query on TransactionUsageEntitlement fail in release 264?▼

Release 264 removed ChargeForOverage, DrawdownOrder, RatingFrequencyPolicyId, and UsageAggregationPolicyId from TransactionUsageEntitlement. Overage chargeability now comes from UsageOveragePolicy.OverageChargeable via ProductUsageResourcePolicy, and DrawdownOrder moved to ProductUsageGrant.

What is the central object in the Revenue Cloud data model?▼

Product2 is the hub object referenced by nearly every domain, including PriceBookEntry, QuoteLineItem, OrderItem, Asset, RateCardEntry, and ProductUsageResource. It also carries direct BillingPolicyId and TaxPolicyId lookups set by billing and tax data plans.