Reltio Connect

 View Only
  • 1.  Help on Survivorship.

    Posted 10-19-2021 03:13
    Hi,

    In regards to how Reltio show Multiple Sources as winnersystem based on the attribute value to be the same from each source and therefore all sourcesystems are defined as winners.



    We want to archive that in the UI, only one sourcesystem is presented as the winner for OV based on the defined source sequence  and if no attribute value in source on top then next source in sequence should be winner. 

    Do anyone have any suggestions on how we could achieve this? 





    ------------------------------
    Trond Stangeland Lie
    Equinor
    SANDNES
    ------------------------------


  • 2.  RE: Help on Survivorship.

    Reltio Employee
    Posted 10-19-2021 11:19
    Hi Trond, 

    Currently, you are observing all the source systems which have the same winner value contributing to the OV. I understand this is the expected behavior of the platform. 

    Here is the documentation reference:

    Source System. The user provides a priority list of sources. A list of priorities is defined for mapping, if it's absent, it is taken from the priority list of the group. All crosswalks from a source system with the highest priority become winners, all values of those crosswalks also become winners.
    Note: The following apply:
    • If an attribute doesn't have values from sources of the priority list, priority of sources are taken from the source type configuration of the business model.
    • If strategy applied to one value only, this value and its crosswalk become winners, irrespective of whether this crosswalk has a source from the priority list or not.

    Survivorship Rules
    Reltio remove preview
    Survivorship Rules
    When an entity or relationship is the result of previous merges, it contains the aggregation of attributes and attribute values from the contributing objects. As a result, any attribute, whether it be a simple, nested, or reference, may contain multiple values.
    View this on Reltio >
     

    Do you desire to have only the 'first' source system displayed for the contributing value? 

    Expected Behavior:
    From DC - EQ-SAP (source system winner) and ignore (EQ Rats and EQ OCD)
    From Equinor - EQ-SAP (source system winner) and ignore (EQ Rats and EQ OCD)

    Do you observe any unexpected OV values in terms of the winner source? 

    Thanks,
    Shantanu


    ------------------------------
    Shantanu Indra
    ------------------------------



  • 3.  RE: Help on Survivorship.

    Reltio Employee
    Posted 10-19-2021 12:22
    Hi Trond,

    You can use fallback strategies in this case. The documentation is given here Survivorship Rules
    Reltio remove preview
    Survivorship Rules
    When an entity or relationship is the result of previous merges, it contains the aggregation of attributes and attribute values from the contributing objects. As a result, any attribute, whether it be a simple, nested, or reference, may contain multiple values.
    View this on Reltio >
    . Fall back strategy MORE_THAN_ONE will suit your use case.

    Thanks and Regards,
    Nagesh Lakinepally

    ------------------------------
    Nagesh Lakinepally
    ------------------------------



  • 4.  RE: Help on Survivorship.

    Posted 10-19-2021 13:33
    Hi Shantanu Indra,
    To answer you first, 
    Do you desire to have only the 'first' source system displayed for the contributing value? YES, cause in the GUI it seems a little disorganized, Users comment and ask why are all sources shown as winner source system? It is no problem explaining the reason to them, but if there is a possibility to only show one source it will be easier for them to understand the view straight away.  

    AND YES THE BEHAVIOUR BELOW WOULD BE PREFERED.
    Expected Behavior:
    From DC - EQ-SAP (source system winner) and ignore (EQ Rats and EQ OCD)
    From Equinor - EQ-SAP (source system winner) and ignore (EQ Rats and EQ OCD)

    Do you observe any unexpected OV values in terms of the winner source? No there are none unexpected values for OV, so it is just a GUI issue making users question why many systems seems to give OV value, even though they dont, they only have the same attribute value.


    Hi Nagesh Lakinepally, 
    We have tried to use fallbackstrategies but we tried ZERO_OR_ MORE_THAN_ONE and that did not work.

    Did not try that since as explained in the «Creating Match Rules course»
    That MORE_THAN_ONE is striving to produce an OV that is null or a single value (did not want a null value)
    That ZERO_OR_MORE_THAN_ONE is striving to produce an OV that is a single value

    Will try to use MORE_THAN_ONE tomorrow, hope it works.
    Can you explain why the MORE_THAN_ONE fallbackstrategy will work compared to ZERO_OR_MORE_THAN_ONE?

    Thanks & Regards
    Trond S Lie

    ------------------------------
    Trond Stangeland Lie
    Equinor
    SANDNES
    ------------------------------



  • 5.  RE: Help on Survivorship.

    Posted 10-20-2021 02:15
    Hi Nagesh Lakinepally, 
    Thank you for feedback, we have now tried to use fallbackstrategies with both "ZERO_OR_ MORE_THAN_ONE" and MORE_THAN_ONE and neither did work as intended.

    We used this configuration.

    {

                                "attribute": "configuration/entityTypes/Material/attributes/ShortName",

                                "sourcesUriOrder": [

                                    "configuration/sources/EQ_SAP",

                                    "configuration/sources/EQ_OCD",

                                    "configuration/sources/EQ_Rats",

                                    "configuration/sources/EQ_COE"

                                ],

                                "fallbackStrategies": [

                                    {

                                    "attribute": "configuration/entityTypes/Material/attributes/ShortName",

                                    "survivorshipStrategy": "LUD"    

                                    }    

                                ],

                                "fallbackUsingCriteria":"MORE_THAN_ONE",

                                "survivorshipStrategy": "SRC_SYS"

                            },


    If you have any other suggestion it would be greatly appreciated. 

    Thanks & Regards
    Trond S Lie

    ------------------------------
    Trond Stangeland Lie
    Equinor
    SANDNES
    ------------------------------



  • 6.  RE: Help on Survivorship.

    Reltio Employee
    Posted 10-25-2021 08:03
    Hi Trond,

    You can configure survivorshipsAdvancedBehavior on the tenant and validate your requirement.

    Please find the details in https://documentation.reltio.com/matchmerge/advancedstrategiesbehavior.html

    Regards,
    Sampada


    ------------------------------
    Sampada GumanSingh
    ------------------------------



  • 7.  RE: Help on Survivorship.

    Reltio Employee
    Posted 10-25-2021 08:03
    Hi Trond,

    You can try using survivorshipAdvancedBehavior 
    for the tenant and validate your requirement.

    Details have been mentioned here:
    https://documentation.reltio.com/matchmerge/advancedstrategiesbehavior.html

    ------------------------------
    Sampada GumanSingh
    ------------------------------