Author: Amol Shrestha
Sometimes business logic requires there should be no redundancy based on fields like email, postcode or zip-code etc. As such, the data management under setting help us achieve it. The duplicate detection rules beneath data management supports the action.
Once we choose New, a window pops out containing:
Name: rule name
status reason: published/unpublished
Description: the reason that made the creation of rule necessary
Base Record Type: entity such as the email, account etc.
matching record type: same as the base record type used for comparing
Field: record type
Criteria: Exact match
The figure shows the respective fields:
It can be saved and published to bring the rule into life. It can be tested using two equivalents on which a popup window comes into existence revealing a match has been found and do we want to proceed further or discard it. The choice is ours and it respects the option chosen.
If you have any questions regarding this feature, just call our friendly team on 01296 328689 or drop us an email at firstname.lastname@example.org. Our team will be more than pleased to discuss these with you.