Batch of duplicates detection set up

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.

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 in the Contacts module.

The deduplication process of structures and relays is based on the same principle applied for individuals. Here's how to set up the batch to deduplicate them too:

In the Organization context, within the Tools module you can find the Batches programs' Schedule: Open the "Duplicates detection" batch.
In the scheduling pop up menu, activate the new "Duplicate detection of relays and structures" option (at the bottom of the options). Save it by clicking on "Schedule"

After the next completion of the duplicate detection, structures having similar names and addresses will be identified as potential duplicates, and relays of the same structure having similar information will also be identified as potential duplicates.

Here is a list of the different fields of the contact file that are taken into account for the identification of duplicates:

Contacts with a zip code:

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 standardized 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).

Old page - English

Old page - French