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.
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.
User Permissions
Needed
To set up related DMO hydration:
Context Service Admin
If you already have a context definition with a DMO parent-child node tree, it hydrates
the related DMO data automatically. No definition changes are required.
To set up related DMO hydration from scratch:
In Data 360, on the parent DMO's Relationships tab, create or confirm an active
relationship to the child DMO. Specify the foreign key field on the parent, the
cardinality, and the related field (the primary key) on the child DMO.
In Context Service, create or edit your context definition and add the child DMO as
a child node under its parent DMO node in the definition's structure.
Context Service automatically discovers the join fields from the Data 360
relationship metadata. No additional mapping is needed. If Data 360 contains more
than one relationship between the same pair of DMOs, Context Service selects the
first one automatically, consistent with the behavior for standard Salesforce
objects. To specify which relationship to use, configure an explicit join field
mapping on the child DMO in the context definition.
本文章是否解决您的问题?
请与我们共享您的想法,以便我们进行改进!
正在加载
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.