TCC: User Time Zone Import - TimeZoneID Vs. JavaTimeZoneName
(Doc ID 2084784.1)
Last updated on JUNE 28, 2022
Applies to:
Oracle Taleo Platform Cloud Service - SmartOrg (Central Configuration) - Version 19A and laterOracle Taleo Platform Cloud Service - Connect - Version 12C and later
Oracle Taleo Platform - Connect - Version 13C and later
Oracle Taleo Recruiting Cloud Service - Version 12C and later
Information in this document applies to any platform.
Symptoms
A TCC User import to change a user's time zone (TalentUser,ArUser,Timezone) results in a 'success' message. However, when the user account is viewed in SmartOrg the time zone did not actually get changed.
Note: If the import fails with an error message that includes 'expected one element', please see: TCC: Import to set User's Time Zone Fails with "expected one element" Error (Doc ID 2774604.1)
Changes
An export of a User's TimeZone field shows it currently has a value of 'EST'. A subsequent import to update the value to be 'PST' has a 'success' message, but the actual value isn't changed when the user's account is viewed in SmartOrg.
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 |