Context Service resolves parent-child relationships between data model objects (DMOs) in Data 360 and returns complete multilevel data hierarchies in a single hydration call. When you configure a DMO hierarchy, such as member demographics, health plan enrollment, or claims history, Context Service identifies the join fields from Data 360's relationship metadata. Previously, AI agents, recommendation engines, and automations that relied on context definitions received incomplete profiles because child DMO data was unavailable.
Where: This change applies to Lightning Experience in Professional, Enterprise, Unlimited, and Developer editions where Context Service and Data 360 are enabled.
Why: Health Cloud, Manufacturing, and Financial Services customers store hierarchical business data across multiple DMOs in Data 360. With related DMO hydration, you get:
- Complete multilevel profiles for AI-powered workflows, enabling accurate member assessments, care plan personalization, and connected-asset event processing without hallucination from missing data
- Transparent support for zero-copy DMOs, so data in external warehouses such as Google BigQuery, Databricks, or Snowflake hydrates without additional configuration
- Support for the existing Context Node hierarchy model