Forum Discussion
BUG: Changing String to Date/Time = bad data
Hello,
Just noticed this.
Issue:
- I'm in Pacific Timezone (currently on Standard Time which is UTC-7).
- I have date data that imports as a STRING such as "2017-11-01T12:00:00.000Z".
- When I change the data type to Date/Time, the new value of the column is "11/1/2017 5:00:00 AM".
- It should be "10/31/2017 5:00:00 AM".
- This action ADDS 8 hours to UTC instead of SUBTRACTING it.
Unless I'm way off here! Which is a possibility!
Thank you
Explain again why converting:
2017-11-01T12:00:00.000Z
Which is clearly November 1st, 2017 should convert to October 31st again?
3 Replies
Explain again why converting:
2017-11-01T12:00:00.000Z
Which is clearly November 1st, 2017 should convert to October 31st again?
Hi Greg_Deckler. I messed up! I was reading the string 2017-11-01T12:00:00.000Z, as ...12:00:00AM. After changing data type to Date/Time, the new value, of 11/01/2017 05:00:00AM looked like "midnight minus 7 hours" but still on the same day (rather than moving to the previous day).
What I should have realized, is that ...12:00:00 is midday on a 24hr. time scale, NOT midnight. My mistake.
Thank you for the reply!
On this note though... how do I control the translation when moving from a STRING to DATE/TIME data type? I ask because this particular column of data has time info from MULTIPLE timezones, but the translation is blanket. It changes ALL times to my local computers time.
Thank you
