revenue-cloud-data-model

Query and navigate the Salesforce Revenue Cloud schema across 263 objects and 9 domains.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill revenue-cloud-data-model-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenue-cloud-data-model
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/revenue-cloud-data-model
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill revenue-cloud-data-model-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding the Salesforce Revenue Cloud (RLM) data model requires knowing how 263 objects, 4,252 fields, and 674 relationships connect across 9 domains, and release-to-release schema changes (such as the 262 to 264 field removals) silently break queries and integrations built on outdated assumptions. ## Core Features & Use Cases - Domain-Organized Schema Reference: Per-domain reference files cover PCM, Pricing, Rate Management, Configurator, Transactions, DRO, Usage, Billing, and Approvals with object tables, key fields, and relationships. - Cross-Domain Relationship Maps: Documented foreign key paths show how Product2, Account, PriceBook2, UsageResource, and LegalEntity connect domains, plus the full quote-to-cash object lifecycle. - Verified Release Deltas: Field-level 262 to 264 changes are recorded with migration guidance, such as usage policy bindings moving to ProductUsageResourcePolicy. - Use Case: When writing a SOQL query to resolve overage chargeability for a usage entitlement, look up the Usage domain file to learn that 264 sources it from UsageOveragePolicy via ProductUsageResourcePolicy rather than the removed TransactionUsageEntitlement.ChargeForOverage field. ## 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?

Run python scripts/ai/query_erd.py relationships Product2 to list all objects linked to or from a given object, or use the path command to find the relationship chain between two objects. Cross-domain foreign keys are also documented in cross-domain-relationships.md.

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 from 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, the ERD covers canonical platform schema only and excludes all __c custom fields by design, including project-deployed RLM_*__c fields. To verify a custom field exists, query the org directly with sf sobject describe.

Why does my SOQL 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.

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 BillingPolicyId and TaxPolicyId set by billing and tax data plans.

How do I query the Revenue Cloud schema without a Salesforce org?

Use the committed erd-data.json snapshot with scripts/ai/query_erd.py, which supports describe, relationships, domain, path, search, and stats commands offline. Live org introspection requires the Salesforce DX MCP run_soql_query tool.