Applies to
Reltio MDM tenants where an attribute, such as a nested Email, uses a Recency (LUD) survivorship rule and is loaded with POST /entities?options=partialOverride.
How to read the Sources panel.
The Sources panel on a profile has two sides. They are often misread. The right side of a panel is not considered the historical record of attribute values. A historic record is in the activity panel.
- Left side (attributes and OV): the surviving values the profile shows. Each attribute displays the value that won survivorship, flagged
ov: true. If survivorship works as intended, an attribute that takes one value shows one value here. - Right side (source swimlanes): every value currently stored on the profile, grouped by the source crosswalk that contributed it. Each value is flagged
ov: trueif it won survivorship orov: falseif it lost. A swimlane can show several values from the same source.
The right side is not a change history. It does not show what the value used to be over time. It shows what is stored on the profile now, per source, including values that lost survivorship. A value appears there only while it still exists on the profile. If a value was replaced or removed, it does not appear on the right.
The actual change history of a value is in two other places:
- Activity Log (
GET {tenantURL}/entities/{entityId}/_activities), which has limited retention (3 months in the tenant we tested). - Historic slice / entity history in the UI.
For this issue, that means:
- Two
ov: trueemails on the left (or the right) means survivorship did not pick a single winner. This is the defect. - One
ov: trueand oneov: falseemail under the same source on the right is the healthy result of the fix below. Theov: falseemail is a retained non-winning value, not a history record.
Symptoms
- A profile shows two or more Email values that are both
ov: true. - The issue started after the load changed from plain
POST /entitiestoPOST /entities?options=partialOverride. - The two values sit on the same source crosswalk.
- The Activity Log delta for the change is
ATTRIBUTE_ADDEDfor the new email, notATTRIBUTE_CHANGED. singleAttributeUpdateDatesis empty ({}) on the entity.
"Email": [
{
"value": { "Type": [ { "value": "Personal" } ],
"Email": [ { "value": "test@gmail.com" } ] },
"ov": true
},
{
"value": { "Type": [ { "value": "Personal" } ],
"Email": [ { "value": "test123@gmail.com" } ] },
"ov": true
}
],
"crosswalks": [ { "type": "configuration/sources/SourceA", "value": "JOEY-TEST-001" } ],
"singleAttributeUpdateDates": {}Cause
Without a nested key attribute, partialOverride with enableNestedPartialOverride: true appends a changed nested value instead of replacing the old one. Both emails then sit on the same crosswalk.
The Recency rule compares update dates. When the load request includes updateDate, Reltio does not write per-value dates to singleAttributeUpdateDates, so both values tie. The fallback rule can also tie when both values share the same crosswalks. A tie leaves both values as OV.
How to investigate
- Get the entity and check
ovandcrosswalkson each Email value, plussingleAttributeUpdateDates:GET {tenantURL}/entities/{entityId} - Check the Activity Log for the change that added the second email:
GET {tenantURL}/entities/{entityId}/_activitiesATTRIBUTE_ADDEDonEmail/Emailconfirms an append.ATTRIBUTE_CHANGEDconfirms an in-place replace. - Check the load request. Look for
options=partialOverride, whether the crosswalk or attributes includeupdateDate, and whetherupdateAttributeUpdateDatesis used. - Check the L3 configuration. Look at the survivorship rule on the attribute, and at
keyAttributeURIson the nested attribute. An empty list means no replace-in-place. - Check the physical configuration for these items:
enableNestedPartialOverridesurvivorshipAdvancedBehaviorupdateAttributeUpdateDatesOnActualChanges
{
"enableNestedPartialOverride": true,
"survivorshipAdvancedBehavior": ["LUD"],
"updateAttributeUpdateDatesOnActualChanges": true
}How to fix it
Choose based on whether the old value must stay stored on the profile as a non-OV value.
Option A: Keep the old value stored and show one OV (recommended)
Enable Advanced LUD in the physical configuration:
"survivorshipAdvancedBehavior": ["LUD"]
This is tenant-wide. A value with a newer singleAttributeUpdateDate on the same crosswalk then wins alone. Test its effect on other LUD attributes before production. Reltio guidance recommends a reindex after the change. Contact Reltio Support before running a full tenant reindex.
Change the load so Reltio stamps the changed value:
- Use
options=partialOverride,updateAttributeUpdateDates. - Do not send
updateDateon the crosswalk or in the entity attributes.
Payload that causes the problem (includes updateDate):
[{
"type": "configuration/entityTypes/Person",
"attributes": {
"Email": [ { "value": { "Type": [ { "value": "Personal" } ],
"Email": [ { "value": "test123@gmail.com" } ] } } ]
},
"crosswalks": [ { "type": "SourceA", "value": "JOEY-TEST-001",
"updateDate": "2026-02-20T07:00:00.000+00:00" } ]
}]Payload that works (no updateDate):
[{
"type": "configuration/entityTypes/Person",
"attributes": {
"Email": [ { "value": { "Type": [ { "value": "Personal" } ],
"Email": [ { "value": "test123@gmail.com" } ] } } ]
},
"crosswalks": [ { "type": "SourceA", "value": "JOEY-TEST-001" } ]
}]POST {tenantURL}/entities?options=partialOverride,updateAttributeUpdateDates
Result in the Sources panel: the left side shows only the newest email (test123@gmail.com, ov: true). The right side, under SourceA, shows test123@gmail.com as ov: true and test@gmail.com as ov: false.
Side effect: omitting updateDate makes the crosswalk date the load time, not the source system’s date.
Option B: One email only, nothing retained on the profile
Set a key attribute on the nested Email in the L3 configuration:
"keyAttributeURIs": [ "configuration/entityTypes/Person/attributes/Email/attributes/Type" ]
A partialOverride load then replaces the matching nested value in place (ATTRIBUTE_CHANGED). Only one email per Type per crosswalk is kept. The old value is gone from the profile and from the right side of the Sources panel. It remains only in the historic slice and the Activity Log. This setting is tenant-wide.
Fixing profiles that already show multiple OV values
Profiles that already hold multiple OV emails will not correct on their own:
- Their emails have no per-value dates (
singleAttributeUpdateDatesis empty), so Advanced LUD has nothing to rank. - Enabling Advanced LUD does not backfill dates.
- A reindex, including a full tenant reindex, also does not backfill dates.
The only way to correct existing profiles is to reload them from the source system. The reload must use the corrected pattern from Option A: options=partialOverride,updateAttributeUpdateDates, with no updateDate on the crosswalk or in the entity attributes. That stamps the current email, so it wins as the sole OV, and the other emails remain as non-OV values.
Plan the reload as follows:
- Identify the affected profiles. For example, search for Person entities with more than one OV Email.
- Make the Advanced LUD change and the payload change live first, then reload.
- Confirm on a two-email profile in a test tenant before running it in production. In particular, check whether re-sending an unchanged email is stamped while
updateAttributeUpdateDatesOnActualChangesistrue. If it isn’t, the reload may need a real change in the payload, or the flag may need to befalsefor the run. - Do not use the Delete Attribute API for cleanup. It removes the stored value and its history.
Things that do not fix it
partialOverride,preserveURIs, when the incoming value already exists on the crosswalk. There is nothing to change.- Changing
updateAttributeUpdateDatesOnActualChangesalone. The flag is only considered whenupdateDateis not in the request. - Reindexing alone. It does not stamp the dates.
Comments
Please sign in to leave a comment.