Hi Trevor,
If I may ask, why do you need the Oldest fallback strategy in the below set up? If you rank the values, shouldn't it only return one value? Unless perhaps, you expect the attribute to have values that will not be ranked.
"The survivorship on Organization Lifecycle is set to use value-based priority and then fallback to Oldest."
The only survivorship rule that is currently somewhat entity-based is the "WinnerEntityCrosswalk" rule.
"The entity value of the current winning entity becomes the winner. All crosswalks from the winner entity also become winners.
If the winner entity is explicitly specified in the explicitWinner parameter, then after the merge the winner's OV is set to true and the loser's OV is set to false. If the winner is not explicitly specified in the explicitWinner parameter, then after the merge the oldest entity is selected as the winner. The winner's OV is set to true and the loser's OV is set to false. For more information, see Merging Two Entities."
https://docs.reltio.com/en/objectives/resolve-potential-matches/potential-matching-at-a-glance/potential-matching-navigation/design-survivorship-rules/survivorship-
------------------------------
Bryant Barrenechea
Solution Architect | Professional Services
------------------------------