Document Check-in via IdcCommand Does Not Recognize Accented Characters
Last updated on NOVEMBER 03, 2016
Applies to:Oracle WebCenter Content - Version 10.1.3.5.0 and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
You are using IdcCommand to check in documents, and you have custom Metadata fields with options lists. Some of the list values contain accented characters, like é and è.
If the option list is validated, the import fails with this error:
If the list is not validated, the import is successful but the accented characters are replaced with the ANSI "block" character. These issues do not occur when checking files in via the browser interface.
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