LongText Field In URM Incorrectly Formatting Plain Text Value As A Date Value
Last updated on OCTOBER 07, 2016
Applies to:Oracle WebCenter Content - Version 10.1.3.3.0 to 10.1.4.5.0 [Release 10gR3]
Information in this document applies to any platform.
When a value is assigned to a batch in the Oracle Document Capture 10g application and committed to URM or UCM, the value is being interpreted (incorrectly) as a date value. The index field set as the mapped to field for URM is a plain text, LongText field type.
This is visible in the user interface and in the database.
Why is URM interpreting the index value incorrectly from ODC? It should be a plain text value and keep it that way, but it is not doing so.
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