OpenProtocols DAVClient Limitations

The OpenProtocols DAVClient (http://www.arpdev.com) has similar limitations to those described in Outlook CalDAV Synchronizer Limitations, however, note the following differences:

1. Data loss might occur. Unlike the CalDAVSynchronizer CardDAV client, data loss for the OpenProtocols DAVClient occurs for custom label entries after download synchronization.

2. Duplicate data might occur. The OpenProtocols DAVClient CardDAV client expects the vCard entries to be in a certain order (for example: Email addresses in home, work, and other order). If data is not in this order, then duplicate email addresses appear for the Outlook contact.

3. Duplicate contacts might appear after upload synchronization to the server. In some cases after updates are made to the contact in Outlook, the OpenProtocols DAVClient CardDAV client uploads the changes using different UIDs (sometimes the original UID.vcf is used, sometimes a totally different UID is used), and this causes the upload synchronization to create a new or duplicate contact on the server.

   For example, if you create a new contact on the Outlook CardDAV client, save, and then update the home email, save, and then update the work email, the CardDAV client upload synchronization contains the following UIDs:

   • Create a new contact with home and work emails: UID:f311065b-0c76-437e-9bc6-2637449c590a

   • Update the home email on the original contact: UID:f311065b-0c76-437e-9bc6-2637449c590a.vcf

   • Update the work email on the original contact: UID:f311065b-0c76-437e-9bc6-2637449c590a.vcf.vcf

   On the server, there are 3 contacts and each contact has a different email. On the client, there are 3 contacts and two of the contacts are identical.