Reltio Connect

1. You can edit the record, make a change (e.g. add a description - it doesn't matter what the change is) and save it. This will cause the match rules for that record to be re-evaluated, and if an automatic match rule is triggered the records will be merged. In this situation the match rules are re-evaluated for only this single record.
2. You can run the rebuild match table from the console task management application. This will reevaluate all the match rules in the system. This is best practice after you change a match rule. However, use with caution, it has system wide impact, so make sure you understand the consequences. You would typically only use this when developing match rules on a small subset of data in a development environment. Don't use in production unless you are absolutely certain of what you are doing.

------------------------------
Terence Kirk
------------------------------

Original Message:
Sent: 5/21/2021 5:37:00 PM
From: Terence Kirk
Subject: Match Rules are not triggered after they are changed

I get asked this question often by people taking Reltio Training.

The OOTB match rules for the Reltio Accelerators (Account 360, Identity 360 etc) are provided as a starting point for developing your own match rules. Use or modify those that support your business requirements, delete those you don't need . They are designed to handle some common scenarios for matching e.g. Contact First Name, Last Name and email address are the same. In order to prevent accidental merges, the OOTB match rules are mostly set by default to "Suspect". So if you look at the Potential matches view they will be flagged as potential matches, which means they should be evaluated by a data steward and either merged manually or flagged as not a match:

If you change a match rule to e.g. "Automatic" after you have loaded data, the match rules will not be re-evaluated automatically, and you will not see any change in the data because of the change you have made to the match rule. You have to trigger the match rule evaluation yourself. There are a couple of ways to do this:

1. You can edit the record, make a change (e.g. add a description - it doesn't matter what the change is) and save it. This will cause the match rules for that record to be re-evaluated, and if an automatic match rule is triggered the records will be merged. In this situation the match rules are re-evaluated for only this single record.
2. You can run the rebuild match table from the console task management application. This will reevaluate all the match rules in the system. This is best practice after you change a match rule. However, use with caution, it has system wide impact, so make sure you understand the consequences. You would typically only use this when developing match rules on a small subset of data in a development environment. Don't use in production unless you are absolutely certain of what you are doing.

------------------------------
Terence Kirk
------------------------------

When records are updated in a tenant (e.g. because of a data load), that  trigger match rules for any records that get updated. That may be the reason you had some records merge.  There is a way to turn off automatic match rule evaluation in a tenant, but this is usually done for an Initial Data Load or if you are doing a bulk load. The idea is that you turn off match rules, do your bulk load, and then run rebuild match rules.

However when making changes to match rules, best practice is to first do a test in a dev environment. Change your match rule to "suspect",  load your data (make sure that the data set contains examples of all business scenarios), review the Potential Matches generated, tweak your match rule further if needed, and repeat. Once you are confident the match rule is working the way you want, change it back to automatic, and move it to production.

------------------------------
Terence Kirk
------------------------------

Original Message:
Sent: 05-24-2021 10:45
From: Angela Wawrzaszek
Subject: Match Rules are not triggered after they are changed

We recently has this scenario, where we were changing an automerge rule slightly.   Technical did the change in Production vs. Test,  and we did not run the Match Rebuild rule, however multiple records automerged and unfortunately our rule was not quite right so we have a cleanup on our hands to undo the merges.   Is there a way to ensure a change to a match rule does not take affect until the rebuild is run?

 

The other possibility is we had an update to our 3^rd party data set after the rule was changed, which could have caused many updates to the data to come in – would that also trigger the automerge rule to take effect without doing the match rebuild?

 

Thank you!

 

Angela Wawrzaszek
MDM Manager 
Master Data Management - Data standardization and process alignment 

+1 315.291.3565 office 
Angela.Wawrzaszek@Hillrom.com 

 

hillrom.com 

 

 

 

CONFIDENTIAL NOTICE: If you are not the intended recipient of this message, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this communication. This communication may contain information that is proprietary, attorney/client privileged, attorney work product, confidential or otherwise legally exempt from disclosure. If you have received this message in error, please notify the sender immediately either by phone or by return e-mail, and destroy all copies of this message, electronic, paper, or otherwise.

Original Message:
Sent: 5/21/2021 5:37:00 PM
From: Terence Kirk
Subject: Match Rules are not triggered after they are changed

I get asked this question often by people taking Reltio Training.

The OOTB match rules for the Reltio Accelerators (Account 360, Identity 360 etc) are provided as a starting point for developing your own match rules. Use or modify those that support your business requirements, delete those you don't need . They are designed to handle some common scenarios for matching e.g. Contact First Name, Last Name and email address are the same. In order to prevent accidental merges, the OOTB match rules are mostly set by default to "Suspect". So if you look at the Potential matches view they will be flagged as potential matches, which means they should be evaluated by a data steward and either merged manually or flagged as not a match:

If you change a match rule to e.g. "Automatic" after you have loaded data, the match rules will not be re-evaluated automatically, and you will not see any change in the data because of the change you have made to the match rule. You have to trigger the match rule evaluation yourself. There are a couple of ways to do this:

1. You can edit the record, make a change (e.g. add a description - it doesn't matter what the change is) and save it. This will cause the match rules for that record to be re-evaluated, and if an automatic match rule is triggered the records will be merged. In this situation the match rules are re-evaluated for only this single record.
2. You can run the rebuild match table from the console task management application. This will reevaluate all the match rules in the system. This is best practice after you change a match rule. However, use with caution, it has system wide impact, so make sure you understand the consequences. You would typically only use this when developing match rules on a small subset of data in a development environment. Don't use in production unless you are absolutely certain of what you are doing.

------------------------------
Terence Kirk
------------------------------