A discourse on dating from a to z

This is a major problem as the users of my queries download the CSV and import into Excel, which cannot deal well with these formats. previously, my_date_field::date, or date(my_date_field) or date_trunc('day', my_date_field) would give the date as YYYY/MM/DD.

Now, i get either 'Monday, 16th May, 2016 AM' or '2016-05-16T.000Z' or a combination of the two.

Once deployed, you can either wait a minute for the timer to trigger, or push the virtual button.

Once you do, the debug tab will populate with the current workflow payload.

In this case, we're adding the response from the HTTP request to the property on the payload.

This new field will then be available to all nodes that come after.

The high level of what this workflow will do is: All workflows start with some kind of trigger. Drag a timer node onto the workflow canvas and set the interval to once per minute.

Both when I pull a sql query, and when I am using the automated metabase filters, I still get the same issue as Ind IAJ. It’s weird because the column in question is just a date with no timestamp, but in the GUI and downloading csv/xlsx metabase adds a time.

Can you explain to me why this has changed and how I can shorten the date format without using to_char ? I don't know if we made any specific changes, but we did fix a few bugs related to date times in GUI queries so something might have broken.

Can you help us by coming up with a sql query against our sample dataset to reproduce the issue?

We'll be using the HTTP node to request data from Discourse.

The HTTP node requires the URL to request and the location on the payload to put the response.

Leave a Reply