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