Known Limitations for Siebel CardDAV Dynamic Mapping

The known limitations for Siebel CardDAV dynamic mapping include the following:

1. The First Name and Last Name fields are required fields for a Contact in Siebel.

   The CardDAV client data upload synchronization fails if one or both of these fields are not specified. The CardDAV client will not notify the user about the error during data upload synchronization. Users must make sure that both First Name and Last Name fields are filled in for new Contacts on the CardDAV client.

   The sample code in the SiebDAV_vCardXMLToXMLDoc.xsl file defaults the First Name and Last Name field to "---" if the field is empty. Customers can enable the section of code as required

   Data download synchronization is blocked until the invalid contact data (that is, the empty Last Name field) is fixed or the invalid contact is deleted.

2. Data upload synchronization failure occurs if an identical StreetAddress and City are entered for different countries.

   The root cause of this is a duplicate key violation for the Address Name field. The Address Name field is constructed from the StreetAddress and City fields based on several calculated fields in the CUT Address business component. Customers must review the CUT Address business component to see if they need to change the construction of the Address Name field or not.

3. (Android only). After a data upload synchronization failure, the subsequent creation of valid contacts will result in duplicate contacts being created on the server through any future data upload synchronization.

   The root cause of this is that the Android CardDAV client resends the PUT request of the same contact with a different UID. The iOS CardDAV client does not have this issue because iOS CardDAV clients resend the same contact with the same UID.

4. When uploading the Contact's Prefix data to Siebel, the data is converted to LIC (language independent code) before saving the data in Siebel. If the data cannot be converted, then the prefix data is discarded. Invalid prefix data cannot be saved (because picklist is bounded) in Siebel.

5. When uploading the Contact's Suffix data to Siebel, the data is converted to LIC (language independent code) before saving the data in Siebel. If the data cannot be converted, then the suffix data is discarded. Invalid suffix data cannot be saved (because picklist is bounded) in Siebel.

6. Uploading a Contacts' Company data is supported only for newly created contacts. Any updates made to the Company of an existing Contact are ignored and are not uploaded (or synchronized) to the server.

7. The iOS and Android CardDAV clients do not support the custom label for the Phone/Fax type. If a user creates a Fax number with a non-default type (for example: Personal, Campus, or Dormitory) in Siebel, it becomes an other fax type on the iOS and Android CardDAV client after synchronization. Eventually on the Siebel side, the type will be updated to Other type implicitly.

8. If PhoneNumber, FaxNumber, EmailAddress, or URL data is not specified, then those entries are ignored and the information is discarded during upload synchronization to Siebel.

9. US State data can be any text that the user enters on their device. If the US State data entered cannot be converted to the Siebel State LIC (language independent code), then it cannot be saved to the state field because the State field picklist is bounded. To prevent data loss, Siebel appends the unrecognizable US State name after the StreetAddress 2 field, and the data is separated with a comma (", ").

10. If the Country Name data entered (for example, Montenegro) cannot be converted to the Siebel Country LIC (language independent code), then it cannot be saved to the country field because the Country field picklist is bounded. To prevent data loss, Siebel appends the unrecognizable Country name after the StreetAddress 2 field, and the data is separated with a comma (", ").

11. For Siebel Address, Country is not a required field. If the Country field is empty after data download synchronization to the iOS client, then it will default to the current Region of the iOS device.

    Using the United States region as an example, if the issue occurs for an address created on the iOS client where the Country (for example: Montenegro) data is not supported by Siebel. After data upload synchronization to Siebel, the Country field data is empty. Then after data download synchronization to the iOS CardDAV client, the Country field data is United States.

12. The Siebel contact Address does not have an additional field to hold a custom label. As a result, the Address entry with custom label will become an empty (no value) Address type in Siebel. And the custom label defined in the CardDAV client is cleared or lost after data upload synchronization to Siebel Server. Eventually after data download synchronization, all address custom labels become Other type in the CardDAV client.

13. (Android only). The Android CardDAV client does not include the display language of the device when sending requests (in the HTTP header's "Accept Language" property) to Siebel. As a result, Siebel sends back only the Address Country name in en-us display to the Android CardDAV client. This is not an issue for the iOS CardDAV client.

14. The Google Maps Geocoding API does not always handle PO Box. Apt#, or Unit# data as expected. In some cases, this data is lost after API processing.

15. The Google Maps API may return more than one address. All matching addresses returned from Google are added to Siebel. Multiple returned addresses are cleansed separately later.