KCS - Issue: Old importer does not recognize or import information when accented characters are present in data

Issue:

  • Unable to import custom fields when data contains special characters, such as accented characters

Environment:

  • Clio Web App

Additional Information:

When accented characters (e.g., é and è) are present in the Contact name, custom fields will not import for that Contact. If the custom fields data includes any accented characters, those characters will not display on a Mac, or will appear as boxes on a PC.

Cause:

At present, Clio's importer does not support the use accented characters, and may not import characters from extended ascii character sets. 

Workaround:

No workaround is available at this time

 

Was this article helpful?
This information is confusing or wrong
This isn't the information that I was looking for
I don't like this functionality