Chirantan,
As you know, Survivorship currently considers only the source system, not the source table. I recommend introducing distinct source system names, such as SourceSystem_TABLEA and SourceSystem_TABLEB. This approach will simplify the process.
However, if you still prefer to work with a single source system, consider adding an additional attribute called sourceRank. Assign a rank of 1 to SourceTableA and 2 to SourceTableB. You can then use functions like Min or Max to determine the preferred source system, and use either primaryAttributeURI or otherWinnerAttributeCrosswalk to identify the actual value for the survivorship.
That said, this approach becomes more complex as more systems are onboarded. My recommendation is to treat each table as a separate source system for better scalability and clarity. Please discuss with the business team and design accordingly.
Thanks
------------------------------
Radhakrishnan Ramalingam
Majix Solutions
San Ramon, CA
https://majixsolutions.com------------------------------
Original Message:
Sent: 05-09-2025 12:15
From: Chirantan Kundu
Subject: Survivorship using priority by source system along with source tables
A customer has multiple source systems where some of the source systems have multiple source systems. The requirement for a survivorship is to consider the order of priority not only by source systems but also by the tables within that source. Is there any way to achieve this without configuring each source system - source table combination into a separate source system?
------------------------------
Chirantan Kundu
Imidia Inc
------------------------------