function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
KSadlerKSadler 

Outlook Edition Best Practices for Public read/write org

Hello,
 
One of our clients is implemeting salesforce.com with public read/write access for accounts & contacts.  They also have deployed Outlook Edition for all users.
 
Many duplicate contacts (owned by separate users) have been the outcome of the entire org synching their outlook contacts to Salesforce.  Once anyone sees this, they tend to immediately merge these duplicates.   When Outlook is synched again, the contact will either be placed back into Salesforce, or the user will be asked if they want their contact deleted from outlook.
 
Does anyone have any suggestions for how the synch settings should be set to best handle this situation and prevent so many duplicate contacts?
 
thanks in advance!
 
Keith
AndrewPhilAndrewPhil
no solution but somewhat of a similar problem. interested in hearing what the response is.
JCoppedgeJCoppedge
Same issue here, and the end result is that our reps only sync their information to their accounts.

I wanted management to import and share their contacts but this just ended up creating duplicates.  The best solution would be to use SF.com as your centralized host for contact information... then create a sync group but this would result in 5000+ contacts and overload a Blackberry.