Reltio Connect

 View Only

  • 1.  Negative Rule Configuration

    Reltio Partner
    Posted 10-14-2022 05:26
    Hi Everyone,
    We have a requirement to configure Negative Rule on the business requirement.
    The Requirement is that whenever the record has an attribute status which is not 5 and 6 then the records should not merge but if the status is 1,2,3,4,78,9,10, 11 then the records should merge. 
    We have configured the below Negative Rule but Reltio Team has confirmed that Negative Rule does not work with standalone 'equals' or 
    'notEquals'
{
"uri": "configuration/entityTypes/Customer/matchGroups/Negative_Test",
"label": "D&B related : Negative on Status",
"type": "automatic",
"negativeRule":
{
"notEquals":
[
{
"values":
[
"1",
"2",
"3",
"4",
"7",
"8",
"9",
"10"
],
"uri": "configuration/entityTypes/Customer/attributes/Status"
}
]
},
"scoreStandalone": 0,
"scoreIncremental": 0
}​


    After checking with Reltio they suggested to have 'notExcatSame' and 'equals' on the Negative Rule and we have configured it similarly as shown:
    {
"uri": "configuration/entityTypes/Customer/matchGroups/NegativeDUNS_Test",
"label": "D&B related : Negative match by D-U-N-S number and Status",
"type": "automatic",
"negativeRule":
{
"notExactSame":
[
"configuration/entityTypes/Customer/attributes/DUNSNumber"
],
"notEquals":
[
{
"values":
[
"1",
"2",
"3",
"4",
"7",
"8",
"9",
"10"
],
"uri": "configuration/entityTypes/Customer/attributes/Status"
}
]
},
"scoreStandalone": 0,
"scoreIncremental": 0
}​

    Finally after checking internally Reltio team has denied that the requirement cannot be achieved by Negative Rule and we should use the attribute in all the regular rules.

    Is it possible to have Negative Rule on Status attribute, where the attribute value is 5 and 6 then the directive is to not merge and if the value is not 5 and 6 then the records can merge.

    ------------------------------
    Sheshadri V
    Fresh Gravity
    ------------------------------


  • 2.  RE: Negative Rule Configuration

    Founding Member
    Posted 10-14-2022 10:25

    Negative match rule is not recommended unless its a last resort. 

    If above is not supported then as a workaround you can try following in your automatch rule and have another suspect match rule for rest of the status and other attributes

    "not": {
    "and": {

    "in": [
    {
    "values": [
    "5","6"
    ],
    "uri": "....."
    }
    ]
    }
    }



    ------------------------------
    Ashish Rawat
    Manager
    Fresh Gravity
    Bangalore
    ------------------------------

    Original Message


  • 3.  RE: Negative Rule Configuration

    Reltio Partner
    Posted 10-17-2022 01:08
    Hi Ashish,

    Thanks for the message.
    We understand that Negative Rule is not recommended as it directs all the auto rule and impacts performance.
    Currently we are using the workaround, but the requirement is to have it resolved by Negative Rule. We have almost 6 Auto Match Rules and wanted to have 1 negative rule instead of defining in all the auto rules.
    Wanted to check if anyone has solved the above use case using notExactSame and equlas combination in negative Rule.

    ------------------------------
    Sheshadri V
    Fresh Gravity
    ------------------------------

    Original Message


Related Content