Destination Records No Longer Being Auto-Created After Update to 16.1 Code Stream: java.lang.String cannot be cast to java.lang.Integer
(Doc ID 2166261.1)
Last updated on MARCH 11, 2019
Applies to:
Primavera Unifier - Version 16.1.0.0 to 16.1.0.0 [Release 16.1]Primavera Unifier Cloud Service - Version 16.1.0.0 to 16.1.0.0 [Release 16.1]
Information in this document applies to any platform.
Symptoms
In Unifier : After migrating/updating to Version 16.1
Destination Records No Longer Being Auto-Created After Update to 16.1 Code Stream. The functionality worked until the environment was updated to version 16.1 code stream. When triggered manually (without condition) the functionality also fails.
The following is captured to the Unifier log files: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |