You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the current logic for parsing dates? I'm getting dates in a slashed datetime format like "08/01/2019 10:42:00" and they're not being parsed, which I'm not surprised about.
How would I go about adding this as a recognizable format? I'm interested because there's a bug in the (unchangeable) system being used to generate these CSVs where sometimes the whole file would use US format (mm/dd/yyyy HH:MM:SS) and sometimes international (dd/mm/yyyy HH:MM:SS) and part of figuring out what it is to flag if for the user is that dates would error out.
The text was updated successfully, but these errors were encountered:
Hi.
What is the current logic for parsing dates? I'm getting dates in a slashed datetime format like "08/01/2019 10:42:00" and they're not being parsed, which I'm not surprised about.
How would I go about adding this as a recognizable format? I'm interested because there's a bug in the (unchangeable) system being used to generate these CSVs where sometimes the whole file would use US format (mm/dd/yyyy HH:MM:SS) and sometimes international (dd/mm/yyyy HH:MM:SS) and part of figuring out what it is to flag if for the user is that dates would error out.
The text was updated successfully, but these errors were encountered: