Maintaining a contact base of high quality requires time and being strategic with the information that we choose to collect. One of the most common issues is the unintentional creation of duplicates. Even if Secutix has some strategies in place to avoid this, such as forcing a contact search before enabling the creation of a new contact, sometimes it's not possible to avoid it from happening.
This is why our software has a batch aimed to the identification of potential duplicates: You will only have to check the list of potential duplicates and select the ones you want to merge in order to maintain a clean contact database.
First, we are going to check the "Batch of duplicates detection":
The set up of this batch is done in the Organization context, within the Tools module you can find the Batches programs' Schedule. If it doesn't appear in the list displayed, it means that it has not been activated yet.
- In order to launch it you will have to click on "New" and add a batch of "Duplicates detection" (aka. Détection des doublons).
- Once the batch is saved, you can set it up at your convenience. It is not recommended to run it more than once every 24h. Click here to know more about its set up.
- Every time the batch is run, an algorithm will check the contact base and identify potential duplicates: these contacts will then appear in orange in the contact search screen.
Indicators taken account by the batch for the identification of duplicates
Contacts w
Those contacts that have the following identical elements are considered to be duplicates:
- The role of the contact.
- The SOUNDEX evaluation (phonetization feature of ORACLE) of the names and surnames of the individual contacts.
- The first 35 characters of the standardised address (street number + type of road + street name).
- The zip code with capital letters.
- The country.
- The name of the structure if the contact is associated with a structure (this is an optional element for the definition of the identifier for the duplicate).
Contacts without a zip code but with a mail address
Those contacts that have the following identical elements are considered to be duplicates:
- The role of the contact.
- The SOUNDEX evaluation (phonetization feature of ORACLE) of the names and surnames of the individual contacts.
- The main mail address (“Mail 1” field).
- The name of the structure if the contact is associated with a structure (this is an optional element for the definition of the identificatory for the duplicate).
- In the “Contact” module click “Duplicates control” to find the potential duplicates identified by the system.

- If you click on a line, you could choose the information that you wish to retrieve after the merge and merge these two contacts or tell the system that that is a false-positive (= false-positive).
.png?version=1&modificationDate=1650440184615&cacheVersion=1&api=v2&height=250)
- After the merge, the contact selected as "head of the duplicate" is the one that will remain active and every entity related to the duplicated contact (including its history) will be attached to the head of the duplicate.
Duplicates not detected by the batch
The batch might not identify some duplicates because the criterion for the detection does not store any data. However, you as a human can notice a duplicates pair. What can you do?
- First, enter the contact numbers of the contacts in question and click “Search” on the duplicates management interface. Then, the button “New” will appear.
- Click on the button and enter the contact number of the head of the duplicate (the one that you wish to keep).
- Do the same with the second contact.
- Merge your duplicates choosing which one you wish to keep.
You could detect the duplicates of the structure type in the same way. You can find more information on this website!
Old page - English
Old page - French