Some examples of fields that you should use to prevent duplicates in the Contacts module are the primary email and phone fields. The values in these fields will be unique to the contact that holds them and are important fields to have the system check for duplicate prevention.
Repeated consideration
Next, the user should determine what considerations the system takes to determine that the newly created records are not duplicates. There are two ukraine phone number data options to choose from in this step, detailed below:
Consider duplicate only if all unique fields match – The system checks all unique fields selected in the first step and prevents the creation of a record only if all field values match the values on an existing record.
Treat as duplicate if at least one unique field matches – The system will check all the unique fields selected in the first step and prevent the creation of a new record if any field value matches a value on an existing record.
Check for duplicates in closed records and ignore blank values
The next two checkbox options allow the user mobile responsive design to further dial in their duplicate prevention:
Check for duplicate closed records If this option is enabled, the system will search all records in the system, including closed records, for matching field values to prevent duplicate records from being created.
The Ignore Blank Values option, if enabled, will cause belgium numbers the system to ignore blank field values when checking the selected unique fields. This means that if a blank (empty) field is matched in CRM, it will allow the system to create a new record. For example, if a user is using the Primary Email field in the Contacts module for duplicate prevention, and the Ignore Blank Values checkbox is enabled, the system will still allow the creation of a new record even though technically the unique fields match because they are empty.
Action options for duplicate records created during synchronization
The last option the user has when setting up duplicate prevention is the “Action to take when duplicate records are found while syncing with external applications”. This is an important step in the duplicate prevention process as it is where the user directs the system on how to handle duplicate records found during syncing with external applications. There are three options to choose from in this step, detailed below: