Relationships: Combine Relationships to Reduce Performance Impact

Creating multiple relationships on a type can impact performance. When possible, combine relationships to improve performance.

Creating multiple relationships on a type can impact performance. When possible, combine relationships to improve performance.

When possible, avoid this example, which includes separate relationships for Mouse and Keyboard, two accessories in a product bundle:

1relation mouse : Mouse;
2relation keyboard : Keyboard;

Follow this example, which uses one relationship for Accessories, which can include Mouse, Keyboard, and other accessories.

1relation accessories : Accessories;

Get Started with Revenue Management Developer Resources
Revenue Management Settings
Revenue Management Deployment
Product Catalog Management
Salesforce Pricing
Rate Management
Product Configurator
Product Configurator Standard Objects
Product Configurator Business APIs
Product Configurator Standard Invocable Actions
Product Configurator Metadata API Types
Constraint Modeling Language
Modeling a Generator Set
Core Concepts
Core Concept Examples
Annotation Examples
Constraint Modeling Language (CML) Best Practices
Relationship Cardinality: Specify the Smallest Range Required
Decimals and Doubles: Consider the Impact of Scale on Performance
Variable Domains: Keep Domains as Small as Possible
Calculating Values: Put Calculations Inside of Constraints
Relationships: Combine Relationships to Reduce Performance Impact
Sequence: Use the Sequence Variable Annotation to Specify the Order of Execution
Sequence and Configurable
Automatically Add a Product: Define as a Separate Constraint
Configurator API: Include the Attribute Developer Name When Creating or Updating Attributes
Access Quantity in CML: Cardinality and Attribute Constraints
Pricing Fields Not Supported in CML
Configure Child or Grandchild Products Based on Parent Product
PCG Group Relations: Follow Order in Constraints
Relations Without PCG: Follow Order in Constraints
Relation Aggregates: Stabilize Preferences Using Staged Variables
Virtual Quote Root: Model Cross-Bundle Logic Using a Shared Transaction Parent
Dependent Logic: Use Configurable Variable Annotation to Prevent Premature Default Assignment
Consolidate Multiple Default Configurations
Business-Centric Constraint Modeling Language (CML) Guidelines
Debugging Constraint Modeling Language (CML)
Model Structure
Transaction Management
Advanced Approvals
Dynamic Revenue Orchestrator
Usage Management
Billing
Revenue Management Associated Objects
Previous Versions