Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
Copper Contributor
vincenzo
Posts: 91
Country: United States
Message 1 of 3 (1,041 Views)
Accepted Solution

Importing contacts - duplicate checking

I've read this KB page   http://kb.sagesoftwareonline.com/cgi-bin/sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=1520...

 but cannot understand the duplicate checking process.  How does it work, and what difference does it make what order you choose in the Duplicate Checking dialog?

 

Thanks

Please use plain text.
Platinum Elite Contributor
ghollister
Posts: 6,537
Country: USA
Message 2 of 3 (1,002 Views)

Re: Importing contacts - duplicate checking

Duplicate Checking is enabled by going to Tools/Preferences, clicking Duplicate Checking and checking the box to enable duplicate checking. You can choose up to 3 fields for which you would like to have ACT! check for duplicates. Duplicate checking is done during an import, an export, when you scan for duplicates, or when a new contact is created. Duplicate checking options will not be available in a remote database... these would need to be set on the Publisher database and synced over to the remotes.

 

When checking for duplicates, ACT! will look for an exact match in the field or fields you choose to have checked in your duplicate checking preferences. If you have chosen two or three fields, then the data must match exactly on all fields in order for the records to be a duplicate.

 

The order does not matter when checking for duplicates since the data has to match on all the selected fields, however it is recommended that at least one of the fields used be the Contact field (for the contact name).

 

Greig Hollister
Sage

Note: Effective 6/1/13, Sage no longers provides support for the Act! software

Please use plain text.
Copper Contributor
vincenzo
Posts: 91
Country: United States
Message 3 of 3 (981 Views)

Re: Importing contacts - duplicate checking

OK thanks for clearing that up.

Please use plain text.