Known Limitations for Outlook CardDAV Clients

Note:

Oracle does not support any Outlook CardDAV clients.

Outlook CalDav Synchronizer is a CardDAV client (for more information, see https://sourceforge.net/projects/outlookcaldavsynchronizer/). The recommended synchronization profile option settings for Outlook CalDav Synchronizer are as follows:

Outlook settings. Select the following check box:

Synchronize items immediately after change
Sync settings. Set the following settings:

Synchronization Mode: Outlook <—— ——> Server (Two-Way)

Conflict Resolution: Automatic

To enable Outlook CalDav Synchronizer, define the following user properties for the CalDAV Service business service:

"Supported CardDAV UserAgent Prefix n" = "CalDavSynchronizer"

Select an appropriate number for n.
"CardDAV Put Use Actual ETag: CalDavSynchronizer" = "y"

This optional user property is required for CardDAV clients to make sure that client-side changes will not be overridden by the server data. CalDav Synchronizer must be the same as the supported prefix.

Outlook CalDAV Synchronizer Limitations

Some of the known limitations for Outlook CalDav Synchronizer CardDAV clients are as follows, consult your Outlook CardDAV client vendor for further details:

Outlook CardDAV Client uses the native Outlook Contact UI for users to update contact data. However, Outlook allows only a fixed number of Contact Emails (3), Web pages (1), Phone numbers (16 phones and 3 faxes), and Addresses (3).
Data loss occurs if more than the supported number of contact child entries are downloaded to the Outlook CardDAV client.
- Outlook contact supports only 3 Emails:
  - E-mail: maps to vCard's EMAIL WORK type, Siebel's Business type
  - E-mail 2: maps to vCard's EMAIL HOME type, Siebel's Home type
  - E-mail 3: maps to vCard's EMAIL OTHER type (no type), Siebel's Other type
  Where more than one Business, Home, or Other type Email entry is created on the server, only one entry of each type is kept for the Outlook Contact after download synchronization.
- Outlook contact supports only 1 Web page (URL)
  - Web page: maps to vCard's URL WORK type, Siebel's Business type
  Where more than one Business or Home type URL entry is created on the server, only one entry of each type is kept for the Outlook Contact after download synchronization. The Other type of URL entry is always discarded after download synchronization.
- Outlook contact supports 19 Phone numbers but only 13 of them (10 phones and 3 faxes) are uploaded to the server, 6 phone number type entries are removed from the Outlook contact.
  - Business: maps to vCard's TEL WORK type, Siebel's Business type
  - Business 2: maps to vCard's TEL WORK type, Siebel's Business type
  - Home: maps to vCard's TEL HOME type, Siebel's Home type
  - Home 2: maps to vCard's TEL HOME type, Siebel's Home type
  - Mobile: maps to vCard's TEL CELL type, Siebel's Cell type
  - Other: maps to vCard's TEL OTHER type, Siebel's Other type
  - Pager: maps to vCard's TEL PAGER type, Siebel's Pager 1 type
  - Car: maps to vCard's TEL CAR type, Siebel's Car custom label
  - ISDN: maps to vCard's TEL ISDN type, Siebel's ISDN custom label
  - Primary: maps to vCard's TEL MAIN type, Siebel's Main type
  - Business Fax: maps to vCard's TEL FAX WORK type, Siebel's Business Fax type
  - Home Fax: maps to vCard's TEL FAX HOME type, Siebel's Home Fax type
  - Other Fax: maps to vCard's TEL FAX OTHER type, Siebel's Other Fax type
  - The following 6 Outlook Contact phone number type entries are never synchronized to the server (that is, never sent out by the CardDAV client) and are lost:
    
    Assistant, Callback, Company, Radio, Telex, TTY/TDD type
- Outlook contact supports only 3 Addresses:
  - Business: maps to vCard's ADR WORK type, Siebel's Business type
  - Home: maps to vCard's ADR HOME type, Siebel's Home type
  - Other: maps to vCard's ADR OTHER type (no type), Siebel's Other type (empty type)
  Where more than one Business, Home, or Other type Address entry is created on the server, only one entry of each type is kept for the Outlook Contact after download synchronization.
Outlook Contact cannot display any entries with custom labels sent from the server. Custom label entries are not lost, they are returned for upload synchronization to the server.

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:

Data loss might occur. Unlike the CalDAVSynchronizer CardDAV client, data loss for the OpenProtocols DAVClient occurs for custom label entries after download synchronization.
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.
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.