Hi Reltio Community!
I want to check here to see if other groups have to develop survivorship rules for this scenario.
We have multiple sources loading into the Reltio application, however we need recency rules set up so other attributes from new sources will never win over existing sources unless the existing source is not present.
We attempted to use "sourcesForOv " under the survivorship rule listing the existing sources, and then use a different "sourcesForOv" for the fallback strategy that lists the new sources. Our thinking was if the existing sources did not exist, the fallback sources would be used for OV attributes. In practice we found out a fallback strategy will only consider the sources defined in the primary survivorship rule.
Has anyone else attempted this and found a solution? At the moment we are using arbitrary last update dates on the new sources that are old enough so it never wins recency against existing sources.
If you are just as stuck as we are, please check out our Reltio Idea to establish this behavior and vote!
This sounds like a interesting use case, would you be able to share an example of data to understand the requirement better.
For one source we have definitive attributes for member information such as name, address, phone etc. This source does not include race and ethnicity data.
For the second source, we have more reliable information about race/ethnicity. However, we do not want this source to override the previous source's demographic data if it already exists.
100 Marine Pkwy #275, Redwood City, CA 94065
+1 (855) 360-DATA+1 (855) 360-3282
© 2022 Reltio. All Rights Reserved
Site by eConverse MediaAlso of Interest: Master Data Management (MDM) Reltio Community Reltio Integration Hub Community, Data Management Community Matching, Merge, Survivorship Reltio Workflow Master Data Management (MDM)