This example shows how attribute groups in the SST record are populated and subsequently updated. For more information, see: Attribute Groups.
Example
This table shows the primary attribute and the other attribute in the group.
| Primary Attribute | Other Attribute in Group |
|---|---|
| CEO Name | CEO Title |
| SIC Code | SIC Code Type |
This table shows the available records for a specific party and the values that populate the Single Source of Truth record based on display rules with the Rank method. The setup for the primary attribute determines the setting for the other attribute in the group.
| Attribute | Data Source Ranking | User-Entered Value | D&B Value | SST Value |
|---|---|---|---|---|
| CEO Name | 1. D&B 2. User Entered | Jennie Lee | Jennifer Lee | Jennifer Lee |
| CEO Title | 1. D&B 2. User Entered | CEO | <Not Available> | <None> |
| SIC Code | 1. User Entered 2. D&B | <Not Available> | 2952 | 2952 |
| SIC Code Type | 1. User Entered 2. D&B | <Not Available> | 1977 SIC | 1977 SIC |
Primary attributes in the SST record are populated like individual attributes, but the other attributes in the group are populated based on the primary attributes' data source. For example, the CEO title attribute takes the D&B value, which is nothing, because the primary attribute, CEO name, takes a D&B value.
Attention: The SIC Code and SIC Type group has additional validations. At all times, they both must have values from the same data source or none at all.
This table shows a user overwrite rule for the four attributes. The setup for the primary attribute determines the setting for the other attribute in the group.
| Attribute | Source Systems That Users Can Overwrite |
|---|---|
| CEO Name | D&B |
| CEO Title | D&B |
| SIC Code | <None> |
| SIC Code Type | <None> |
This table describes what happens when a user, who is assigned the above user overwrite rule, tries to enter data. The table shows the SST values from above, the data sources of each value, the highest ranked data sources, as well as the new user-entered values and the new SST values, whether the user updated them or not.
| Attribute | Highest Ranked Data Source | Current SST Data Source | Current SST Value | New User Entered Value | New SST Value |
|---|---|---|---|---|---|
| CEO Name | D&B | D&B | Jennifer Lee | <No Action> | Jennifer Lee |
| CEO Title | D&B | D&B | <None> | CEO | CEO |
| SIC Code | User Entered | D&B | 2952 | 2999 | 2999 |
| SIC Code Type | User Entered | D&B | 1977 SIC | 1987 SIC | 1987 SIC |
The user overwrite rule applies only to attribute values that have D&B as the current SST and highest ranked data source. This table describes which attributes the rule applies to and how attributes within a group can be updated separately except for the SIC code and type group.
| Attribute | Rule Definition | Rule Applies | Description | New SST Data Source |
|---|---|---|---|---|
| CEO Name | Allow Overwrite of D&B | Yes | The user does nothing and leaves the D&B value in the SST record. | D&B |
| CEO Title | Allow Overwrite of D&B | Yes | Even though the primary attribute, CEO name, is still a D&B value, the user can overwrite the D&B CEO title in the SST record. | User Entered |
| SIC Code | Prevent Overwrite | No | Even though the current SST value is from D&B, the user can overwrite it because user entered is the highest ranked source. | User Entered |
| SIC Code Type | Prevent Overwrite | No | The user must also overwrite the D&B SIC code type in the SST record because SIC code and type must always have the same data source. | User Entered |