Combine the power of Data Model Objects (DMOs) from Data 360 with context definitions. When a context definition's node structure mirrors a DMO hierarchy in Data 360, Context Service resolves the parent-child relationship and hydrates every level in a single request.
Required Editions
| Available in: Lightning Experience |
| Available in: Developer, Enterprise, Professional, and Unlimited editions for Industries clouds where Context Service and Data 360 are enabled. |
When your context definition includes parent and child Data Model Object (DMO) nodes, Context Service uses the relationship that you define in Data 360 to hydrate the complete hierarchy in a single request.
You can store related data across multiple DMOs in Data 360. For example, a health plan member's demographics, plan enrollment, and claims history can each live in a separate DMO. When your context definition's node structure mirrors this hierarchy, Context Service hydrates every level in one request instead of requiring a separate request for each DMO. AI agents, recommendation engines, and automations that consume the context get a complete profile.
Related DMO hydration depends on three parts that you configure separately. You define a relationship in Data 360, a node structure in your context definition, and a mapping that connects each node to its DMO. See Set Up Related DMO Hydration.
Considerations for Related DMO Hydration
- A node tree in a context definition can contain entirely DMOs or entirely Salesforce objects. You can't mix Salesforce objects and DMOs within the same tree, although a single context definition can contain multiple trees.
- Data 360 allows only one relationship between a given pair of DMO fields, but a pair of DMOs can have multiple relationships across different field pairs. See Set Up Related DMO Hydration for how Context Service handles multiple relationships between the same two DMOs.
- Context Service caches the resolved relationship with your context definition's version. If you change a DMO relationship in Data 360 after your context definition is active, increment the context definition version so that Context Service picks up the change.
Zero-Copy DMOs
DMOs backed by external data warehouses, such as Google BigQuery, Databricks, or Snowflake, hydrate the same way as native Data 360 DMOs. Context Service reads the same relationship metadata regardless of where the underlying data is stored. For more information, see Zero Copy Data Federation.
- Map to a Custom Data Space
For extended context definitions, switch mapped Data Model Objects (DMOs) from the default Data Space to corresponding DMOs in a custom Data Space in your org. - Set Up Related DMO Hydration
Connect a parent and child Data Model Object (DMO) so Context Service hydrates the complete hierarchy in a single request instead of a separate request for each DMO. Configure the relationship in Data 360, then add and map the child DMO in your context definition.