Product: Omatic Cloud
Description: This solution explains why Omatic Cloud prevents a user from adding a record as new after being identified as a duplicate
Depending on your Record Triage and Matching rules, you will see matches show in the 1:1 or 1:Many matches bucket. These matches are assigned Match Score, which indicates the likeliness that they are a match based on matching fields such as: first name, last name, email, and/or ID.
When processing these matches, if there is a match on lookup ID, or alternate lookup ID, you only have the option to match to an existing record in BBCRM, or your endpoint (such as Luminate Online).
We have an incoming record for John Adamson, and Omatic Cloud is identifying he is a match to Mark Adamson in BBCRM. They share the same email, ID, as well as a partial match on name. Since they have the same Luminate Constituent ID, we will be unable to add them as new to BBCRM. It is recommended that you evaluate which record has the correct ID to prevent overwriting data in your database.
In this scenario, it is recommended that we identify why Mark Adamson's BBCRM record has John Adamson's Luminate ID. If we were to remove John's email from Mark's BBCRM record, then John would go to the New Records bucket, and we can now add him as a new constituent to BBCRM.