Reltio Connect

We currently have Aggregation for the Address.  Within the address attibutes we have Reltio Cleanser or Nothing on Address Line1.

Dropping down to the remaining attributes we have OtherAttributeWinner Crosswalk.

When you have multiple crosswalks and a new or updated crosswalk comes in that has the same AddressLine1 but has <null> for AddressLine 2. what is the expected behavior?  Note:  Address Line 2 at source was entered in error.

The behavior we are seeing is the the AddressLine2 is NOT being reset to null and it doesn't get recleansed.  It retains the AddressLine 2 value that originally came from the same crosswalk in the past.

Question:  Is <null> ignored in the OtherAttributeWinner strategy if there was a value from a different crosswalk and/or removed from source for an existing crosswalk as most recent change?

------------------------------
Sandro Palleschi
Manager - Enterprise Data Services at Empire Life
Empire Life
------------------------------

Hi Sandro,

I think maybe the behavior you are seeing is related to the type of update request you are sending in the API and not necessarily the survivorship. If originally you had sent in a crosswalk that contained a value for AddressLine2 (incorrect or correct) and in a subsequent update that crosswalk provides values for all fields excluding one for AddressLine2 because that was an invalid value in the original post we may see the original value remain if you are using "partial override" option in the API. If you want to fully replace all data from that crosswalk you could remove the "partial override" option and send the new payload as a full override.

Null values should always be ignored by survivorship, so if you have 2 crosswalks contributing to AddressLine2 they should both in theory have data (nulls are not stored in Reltio) and the winner would be driven off the OtherAttributeWinnerStrategy logic.