after the latest update from 0.34.1 straight to 0.37.7 ALL of our Google Sheet integrations broke because the date format populated in CSVs has changed to a UNIX Timestamp (including the T) as outlined in https://github.com/metabase/metabase/issues/10803
as well as Date format is incorrect after download the xlsx and csv file
It is really utterly frustrating when such things suddenly change.
Why can’t we have a configuration for the date format that should be used
(a) for display in the user interface (PLEASE allow for all possible formats by just allowing the admin to configure the format string)
(b) for CSV exports
© for Excel exports
(d) for JSON exports
If you don’t want to put it into the admin interface, at least give an option to set it via a configuration flag during startup or whatever other means.
But changing these things around really breaks stuff and makes using Metabase really frustrating when all of a sudden all your users and colleagues lose access to their data.
Is this something that can be fixed quickly ? I fear we will have to downgrade yet again back to 0.34.1 because the latest updates simply break stuff that takes ages to rebuild.
Thank you & Best Regards