- Last Active
Some follow up on this issue: The data provider has since decided to also provide time granularity. Per the documentation, 'hh' should work: dd-MM-yyyy hh:mm:ss but it does not! Only 'HH' works: dd-MM-yyyy HH:mm:ss
Hi Cody, Domo Support got back to me and advised that the Schema should be set to STRING and not DATE. And this (verbatim) note as well: Note that this is still a string column. You’ll have to convert the data into a date using a dataflow or beastmode on the Domo side. I don't like it that WB cannot have the final column…
Thanks Colt for all your help, I'll be forwarding this very post to DOMO Support.
Tried just that's here's the log: Could not parse date '9/9/2017 12:00:00 AM' from 'dd-MM-yyyy hh:mm:ss tt' Could not parse date '9/9/2017 12:00:00 AM' from 'dd-MM-yyyy'
I tried 'em both, here's what I get Could not parse date '9/9/2017 12:00:00 AM' from 'dd/MM/yyyy' Could not parse date '9/9/2017 12:00:00 AM' from 'dd/MM/yyyy hh:mm:ss tt' It's failing on FIRST line, If you look at the actual values: 1 09-09-2017 2 09-09-2017 3 09-09-2017 4 09-09-2017 5 09-09-2017 6 12-09-2017 7 14-09-2017…
Thanks I tired that, only I think in my case, I'd need d/M/yyyy, but I tried both and none works :( Sounds like a BUG in WB, if you look at the error msg relative to the actual data being passed! Could not parse date '14-09-2017' from 'd/M/yyyy hh:mm:ss tt' Could not parse date '14-09-2017' from 'M/d/yyyy hh:mm:ss tt'…
Thanks Colt for this info, I did set the type already to DATE in the schema. The link you provided was very helpful, I was able to add a transform. Though now, WB is showing different error: Could not parse date '9/9/2017 12:00:00 AM' from 'DD-MM-YYYY' It does not seem right, how does WB changes from how the actual values…