Creating a Child Lookup Node with a One-to-One Relationship
Creating a Child Lookup Node with a One-to-One Relationship
Create a child lookup node with a one-to-one relationship when the parent node contains one child lookup node. You create a child reference node for a gender lookup with a one-to-one relationship to a person.
Before you begin, in the MDM Hub, ensure that you configured the lookup base object and the relationship between the base object of the parent node and the lookup base object.
Click
Business Entity
Modeling
, and then select
Business Entities
.
Select the business entity.
In the tree view panel, select
Lookup Fields
, and then click
Create
.
In the properties panel, enter a node name and a label.
For example, enter
Gender
for the name and label.
From the
Object
list, select the base object that contains the lookup child node data.
For example, select the lookup base object
LUGender
.
From the
Constraint
list, select the relationship between the base object of the parent node and the base object of the lookup node.
For example, select the constraint
C_PARTY(GENDER_CD).C_LU_GENDER(GENDER_CODE)
.
Optionally, configure default values for user roles.
The picklist in
Data Director
defaults to this value for the specified user roles.
Beside the
Default Value
heading, click the
Add
icon.
Enter a default value that matches a value in the selected lookup base object. When entering dates, use the GMT format, such as
2018-06-06T09:34:25.801-04:00
.
The Provisioning tool does not validate the values. You can test the default values from Data Director.
From the
User Role
list, select user roles and then click the
Add
icon. To specify all user roles, select the asterisk (*).
The selected user roles appear. To remove a user role, click the
Delete
icon beside the role.
Optionally, to use this default value with the user roles that have no other default values configured for this field, select
Apply this value to the user roles that have no default value assigned
.
To configure more default values, repeat these substeps.
Click
Apply
.
The changes are saved but are not published to the MDM Hub.