Prevent Syncing New Contacts Marked as Private to CRM

  • Updated

There are two ways to allow users to selectively sync new contacts from Outlook / Exchange to the CRM with Riva. Both of these options work with Riva Cloud and Riva On-Premise.

Option One: Outlook Client "Private" Setting

For customers using the Outlook client or other Exchange clients that support a "private" option, the first option is to use the native client "private" option.

Have the user mark the new contact as "private" when the contact is created. Riva will not synchronize new contacts to the CRM that are created and marked as "private" with the Outlook client.

Option Two: Private Company Name Override

For Exchange clients that do not support the "private" option, including

  • Outlook Web Access,
  • BlackBerry,
  • Mac Entourage, Mac Address Book.

The second option is to use the Private "Company Name" Overrides. This is for users who use email clients, applications, or mobile devices that do not support Exchange Private contacts. This option would be used if contacts are being synced to the Default Contact List and a mobile user wants to create a contact and flag the contact as Private. Adding one of the keywords to the Company field when creating a contact indicates to the sync process that it must not sync this contact automatically to the CRM.

AdvancedOptions-4 (2).png

Riva automatically enables this option and configures it to check for "me", "my", "personal", or "private" as the keywords. Use this option to change the keyword list. Keywords are not case-sensitive.

Riva Cloud default settings

This feature is not visible in the Riva Cloud interface, but it is enabled and set to use "me", "my", "personal", or "private" as the keywords.

Riva Sets Exchange Private Flag (Riva 2.4.29 or higher)

If a user uses the private company name override feature, Riva assigns the Exchange Private flag to the contact in the user's Exchange address book.

Riva 2.4.29 or higher includes an advanced option that can be applied to the sync policy that prevents Riva from assigning the Exchange Private flag but still treats the Exchange contact as private for CRM sync purposes.

To apply: Add the following advanced option key and value to the Riva sync policy:

Sync.Ex.ShouldSetPrivateFlagOnPrivateContacts = true

Was this article helpful?




Article is closed for comments.