Use Data Graph projections to retrieve the specific fields and data model objects (DMOs) you need from your Data Graphs. Projections reduce data transfer sizes and enable you to tailor Data Graph responses for specific use cases like LLM grounding, agent workflows, and downstream applications.
Where: This change applies to Data 360 in Developer, Enterprise, Performance, and Unlimited editions.
When: This change is available in July 2026.
Why: With projections, you can select specific fields across the graph hierarchy, filter records within DMOs using comparison operators, and alias fields to match downstream system requirements. This optimization is valuable for reducing LLM context sizes and improving API performance.
How: Add the projectionFields and
projectionFilters query parameters to your Data Graph lookup API requests.
Specify fully qualified field paths using dot notation from the root DMO, and use comparison
operators (=, >=, <=, >, <) to filter records. For example:
projectionFields=[UnifiedIndividual.ID,UnifiedIndividual.FirstName,UnifiedIndividual.Case.CaseNumber]&projectionFilters=[Case.CreatedDate>='2024-01-01'].
You can also alias fields for downstream integration using the = syntax:
UnifiedIndividual.ID=customer_id.