I'm having a heck of a time parsing some really standard date formats. I've got timestamps coming out of an API in full ISO8601 format:
2017-03-30T09:57:45:963-0700 2017-04-13T15:48:46:034-0700 2017-01-16T14:42:05:811-0800 2017-01-16T14:41:04:640-0800 2017-01-16T14:41:04:640-0800
From what I've found, Alteryx doesn't support milliseconds or timezones, so I've had to throw down a Regex parser to tokenize the dates into their elements:
(\d{4})-(\d{2})-(\d{2})T(\d{2})\:(\d{2})\:(\d{2}):(\d{3})([\-\+]\d{4})
and then use a formula to pull in the values Alteryx can understand and format it:
DateTimeParse([EntryDate_Year] + "-" + [EntryDate_Month] + "-" + [EntryDate_Day] + "T" + [EntryDate_Hour] + ":" + [EntryDate_Minute] +":" + [EntryDate_Second] + [EntryDate_Timezone],"%Y-%m-%dT%H:%M:%S%z")
Is there a better way, or a feature request I should be voting up?
Solved! Go to Solution.
Hey @braxtone - there are also a few ideas that you can contribute to too, several of them around decomposing or recomposing dates; and one about rethinking the way that dates are treated in Alteryx (since there are different date treatments for date parsing; date construction; date trimming; date adding; etc).
There's none that specifically addresses ISO date format, but I reckon you should add it.
Here's the full list of ideas in the IDEAS board related directly to date handlin. Have a look at these, and it would be good to get your thoughts and support on them:
Thanks Sean. I wanted to make sure I wasn't missing something obvious before posting a feature request. I think the idea you put out in https://community.alteryx.com/t5/Suggestions-For-Our-Community/Can-we-group-product-ideas-together-a... is a great one and responded to it.