---
schema_version: "1"
id: 8733704a2db7bbacd71da49131b846a2410883689d90a5f171e4d6462520ae63
title: Special Handling of DMO Relationships in Data Graphs
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_dg_n1_restriction.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_dg_n1_restriction.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c7acb42317c168eb049b83fce8f406860f3ce41fc44508447488fdd71f13b5c3
description: Data model object (DMO) relationships can affect how data is processed and reflected in data graphs, particularly in real-time data graphs. Review DMO relationship types when designing data graphs to make sure that processing behavior aligns with your expected update patterns.
products:
  - Data 360
release: "264"
---
# Special Handling of DMO Relationships in Data Graphs

Data model object (DMO) relationships can affect how data is processed and reflected in data graphs, particularly in real-time data graphs. Review DMO relationship types when designing data graphs to make sure that processing behavior aligns with your expected update patterns.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;release=264.0.0&amp;type=5" title="Data 360 is available in several supported Salesforce editions. Some Data 360 features also require additional licenses.">Data 360 edition availability</a>.</td></tr></tbody></table>

Real-time data graphs support 1:1 and 1:N DMO relationships. An N:1 relationship occurs when multiple child records reference a single parent record. For example, consider the relationship between sale order products and product categories. A sale order can contain multiple products, and each product in the order is represented as a sale order product record. Each sale order product is associated with a product category, such as Electronics or Fashion. A single order might include an iPhone and AirPods, which both belong to the Electronics category, and a T-Shirt, which belongs to the Fashion category.

In this scenario, multiple sale order product records reference the same product category record. For example, both the iPhone and AirPods sale order product records reference the Electronics product category. This relationship represents an N:1 relationship, where many child records map to one parent record. The child record’s foreign key (product category ID) points to the parent record’s primary key, allowing multiple child records to reference the same parent record.

Consider these two scenarios of N:1 relationship support based on when the real-time data graph was created.

- New real-time data graph behavior: Newly created or edited real-time data graphs don’t support N:1 relationships. If adding a DMO introduces an N:1 relationship, the system blocks the selection during creation or editing.
- Existing real-time data graph behavior: Real-time data graphs that were created before this restriction was introduced may already include N:1 relationships. These graphs continue to run for backward compatibility. However, changes to the parent DMO in an N:1 relationship aren’t immediately reflected in related records within the real-time data graph. Updated values become available only after the data graph is rebuilt or refreshed according to its configuration.

This restriction applies only to newly created real-time data graphs. Standard data graphs continue to support N:1 relationships.

#### See Also

- [_Salesforce Help_: Create a Data Graph](https://help.salesforce.com/s/articleView?id=data.c360_a_create_a_data_graph.htm&release=264.0.0&type=5 "Before creating a data graph in Data 360, decide which existing data model object (DMO) to use as the primary DMO. The primary DMO determines which related objects you can include in the data graph.")
- [_Salesforce Help_: Edit a Data Graph](https://help.salesforce.com/s/articleView?id=data.c360_a_edit_a_data_graph.htm&release=264.0.0&type=5 "You can change a data graph’s name and description, associate new data model objects (DMO), and make additive changes to the existing primary and associated DMOs.")
- [_Salesforce Help_: Data Graph Data Structures](https://help.salesforce.com/s/articleView?id=data.c360_a_data_graph_data_structures.htm&language=en_US)