Contacts Migration Adds Additional Backslashes In Data When Commas Present In Contacts (Doc ID 2195387.1)

Last updated on NOVEMBER 14, 2016

Applies to:

Oracle Communications Contacts Server - Version 8.0.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Using:  Contacts Server 8.0.0.2.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:

e1579fc42e66f.vcf
FN:Lastname\\\, Firstname

And the vcard looks like:

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms