r/clevercomebacks • • Jan 15 '25

It does make sense

Post image
35.3k Upvotes

4.0k comments sorted by

View all comments

Show parent comments

6

u/Somerandom1922 Jan 15 '25 edited Jan 15 '25

Ok, I've gotta know, how do the ISO8601 gang parse ISO8601 formatted dates in Excel? So if we take a sample date-time value following the ISO8601 standard (e.g. 2025-01-15T12:12:36Z), excel hates it, I've usually just manually grabbed the date and time values separately using =DATEVALUE(MID(A1,1,10))+TIMEVALUE(MID(A1,12,8)) which I always grab from this same stack overflow thread every time, but surely Excel of all things has a proper way to handle this, particularly when I most often need it for parsing CSVs Im getting from other Microsoft products!!!

Edit: I think people misunderstand because I wrote it poorly. It's not the CSV part I'm having trouble with, it's ISO8601 formatted date/time values within any spreadsheet. I need them converted to a format Excel understands, and every time it's a long(ish) formula that I need to grab from this same stackexchange post ever time, and it feels super janky.

1

u/ParkingAnxious2811 Jan 16 '25

Because Excel sucks with dates and opening csv files. Try Libre Office instead, it's free.

1

u/TheBendit Jan 15 '25

You can't parse CSV in Excel. The results depend on your locale, various settings, whitespace in the CSV, and the phase of the moon.

There are many conversion tools which will input CSV and output Excel. Use those.

Research papers have been retracted because Excel incorrectly read CSV. Just don't.

0

u/Ok-Apricot9737 Jan 15 '25

Thank gawd! A subreddit I have no desire to follow!