Data 360: Understand How the Master Label for DMOs are getting updated

You may experience a discrepancy in the DMO names when viewing it in DMO page and the names displayed on Identity Resolution page and Reports or Dashboards. This may occur because on DMO, you will be able to see the Object Label and Object API Name, However, the other platforms (Identity Resolution, Reports, Dashboards) will display the Master Label which is backend field for the DMO and is not accessible on UI for customers.

Lets look at below example on how this works:

Lets consider two DMOs present in two different data spaces and have two Identity Resolutions created for each DMO.

DataSpace1:
By default, since the default data space will not be available with any Data Space prefix and it will be blank.

Data Space Name: DS1
Data Space API Name: default
Data Space Prefix: (None)

DataSpace2:
Let’s say customer created another data space with below details:

Data Space Name: DS2
Data Space API Name: TESTDS2
Data Space Prefix: PFX

Now, let’s consider Individual DMO as an example. Customer updates mappings for this Individual DMO for a DLO from DS1 data space. Initially the DMO will be available as below:

Object Label: Individual
Object API Name: ssot__Individual__dlm
DeveloperName: Individual
MasterLabel: Individual (Backend field for the DMO)

If customer tried to update the label for the above DMO, let’s say the updated label would be DS1_Individual. The naming would be as below:

Updated label: DS1_Individual

Object Label: DS1_Individual
Object API Name: ssot__Individual__dlm
DeveloperName: Individual
MasterLabel: Individual

The Object label for the DMO will be updated with the "Label Override" value but there will be no change for the Master label.

Now, if customer maps a DLO from DS2 data space to the DMO ‘DS1_Individual’, a new DMO will be created in DS2 data space with below naming convention:

Object Label: DS1_Individual
Object API Name: PFX__Individual__dlm
DeveloperName: PFX__Individual
MasterLabel: DS1_Individual

Let’s say customer changes the label from DS1_individual to “Individual” on UI, the Updated label for this DMO would be ‘DS2_Individual’. However, it will not change the Master Label for the DMO. And, to update the Master label, it will check if there were any Updated label value present for the source DMO and if present, it will be populated with the updated Label value of the Source DMO from which new DMO got created.

Now, the updated names for the new DMO are as below:

Object Label: Individual
Object API Name: PFX__Individual__dlm
DeveloperName: PFX__Individual
MasterLabel: DS1_Individual

Let’s create Identity Resolutions for two data spaces:

RulesetName: IR1
Data Space: DS1
Expected value for Primary DMO might be: DS1_Individual
But, Actual value for Primary DMO would be: Individual

RulesetName: IR2
Data Space: DS2
Expected value for Primary DMO might be: Individual
But, Actual value for Primary DMO would be: DS1_Individual

From the names visible on UI for the identity resolution, it may seem like the IR is pointing to DMOs from different data spaces, but it is pointing the correct DMOs as per the Master Labels of the corresponding DMOs

Note:

1. The Object Label value is the same as MasterLabel during creation. But when the Object Label is edited through UI, that change is reflected in Updated Label only and not on MasterLabel
2. For Standard DMO, When updating the label from the UI, only the Object Label field is updated but not the Master Label.
3. For Custom DMO, When updating the label from the UI, both Master Label and Object Label are updated.
4. MasterLabel doesn't have to be unique, multiple DMOs can have same MasterLabel.
5. If the Object Label for the source DMO is not updated, the MasterLabel for the new DMO will be populated with the MasterLabel of the Source DMO