Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Clarification on Cloud Database Time Zone
Content
Can we run into a scenario where a cloud stored date (without timestamp) attribute could store the incorrect date? For example, if an action was performed by HRIS on a performance review at 10:00 PM EST on the 1st, but the date captured on the non-timestamped attribute would be the 2nd because the database is stored in UTC. My understanding is that the cloud database always stores date/timestamped data in UTC. We can always update preferences globally and for users to default time zones within the UI, but can not update the core database to store the core data in EST.
Tagged:
1