Reltio Connect

 View Only
  • 1.  Survivorship question

    Posted 07-25-2025 08:30

    Here's my situation. Within the Organization entity, we have the following attributes

    • Organization Lifecycle
    • Party ID
      • This is defined as a Custom ID, so it is guaranteed to be unique
      • I only ever want one OV for this

    I also have the following sources:

    • Party Service
    • Reltio

    The survivorship on Organization Lifecycle is set to use value-based priority and then fallback to Oldest. What I'd like for my survivorship rule on Party ID to be almost like the "OtherAttributeWinnerCrosswalk" strategy, but instead of it being tied to the crosswalk, I'd like it tied to the entity. The reason I'd like it this way is that there's no guarantee that the Party ID and Org Lifecycle will share the same crosswalk within a given entity. Either could be created by the Party Service or the Reltio source (with oldest as a fallback).

    My question is this: is there a way to do this with the existing survivorship strategies?



    ------------------------------
    Trevor Burn
    Assent
    ------------------------------


  • 2.  RE: Survivorship question

    Reltio Employee
    Posted 07-29-2025 08:41

    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
    ------------------------------