Contacts Migration Adds Additional Backslashes In Data When Commas Present In Contacts
Last updated on NOVEMBER 14, 2016
Applies to:Oracle Communications Contacts Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Using: Contacts Server 220.127.116.11.0
It seems that entries with commas that are migrated, are stored with a triple (\\\) backslash, delimiting the comma and results in the UI displaying it with a single backslash. While, if you create a new entry with a comma, it is stored with a single backslash to correctly delimit the comma, resulting in the UI not displaying any backslash.
For example, if a user in PAB has:
displayName: Lastname, Firstname
After migration they are stored in the Contacts database as:
And the vcard looks like:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms