The following registry keys (under heading [14748]) must be configured in order to use the automatc deletion of duplicates:
•Guest fields by which identical guests are identified during the automatic merge (First merge run [7463] and second merge run [7464])
These fields determine which profiles are duplicates.
•Guest fields to be transferred to the target guest profile during the automatic merge (First merge run [7463] and second merge run [7464])
If the fields defined here are blank in the target guest profile, then the entries of the records that are about to be deleted will be taken over. If the fields already have an entry in the target guest profile, a comment will be added advising the user that there was a different entry in the deleted profile.
•Do not merge profiles with first arrival in the future [401047]
This setting ensures that guests whose first arrival is in the future are not being merged. As their details may not be complete yet, they may otherwise be merged with already existing guests.
•Merge-rule [2704]
You can opt to keep either the newest or the older record. Generally, one can assume that the recent data is the more up-to-data.
•Search with soundex-algorithm [2704]
Use if required.
•Send merge protocol [7473]
When using Outlook-integration, the results of the merge can be sent to an e-mail address automatically. If you are not using Outlook-integration, you can find the protocol (mergelog.txt) in the SIHOT path, directory log\mergelog.