• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 95 subscribers
  • Views 4828 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Manager - DB Export - Datevalues - Timezone

fatih.eroglu
over 8 years ago

Hello, 

our customer is regulary using the DB Export via Manager and considered for date values a "mismatch" which is explainable due to the different timezones.

To be clearly, we have our date values defined as UTC+1 in our HR Imports. We have the confusion at the customer side, as per standard the database stores it date values in UTC, and the DB Export from the Manager seems to use the native UTC date values.

For Example: 15.02. 00:00 is stored in the database as 14.02 23:00

The object layer is properly validating and calculating the date as 15.02. 00:00

DB Export in manager (Data as UTC)

Object Browser: Data Display (UTC+1) / Data Value (UTC)

 

My Question, is it possible to run the exports by using the proper timezone, or what is the best practice at that point?

Thanks Fatih

Parents
  • 0 over 8 years ago
    1IM uses UTC/GMT for date related attributes, which provides the flexibility to convert timestamp based on the local time zone (w/ daylight saving or standard). The exported date/timestamp could be customized based on local time zone but the customization is required. There are some samples online to convert UTC to local system time zone w/ daylight saving/standard. HTH
Reply
  • 0 over 8 years ago
    1IM uses UTC/GMT for date related attributes, which provides the flexibility to convert timestamp based on the local time zone (w/ daylight saving or standard). The exported date/timestamp could be customized based on local time zone but the customization is required. There are some samples online to convert UTC to local system time zone w/ daylight saving/standard. HTH
Children
No Data