CSV/JSON formatting affected by visual settings

Bug reports
1

Greetings Metabase fellows.

This one was tricky to categorise, so don't mind possibly wrong category. It purely depends on your view of things.

It appears that v49 update has introduced a change that has impacted our user experience somewhat negatively.

Here is an example:
We have an org default in Metabase:

  • separator style set to "100 000,00"
  • dates style is "31 Jan, 2018"

This is the preferred way for us in all the reports we have in Metabase.
However, we rely heavily on automations that utilize JSON or CSV exports from these reports.
And now, since recent version, the JSON do contain the following:

[
  {
    "Created Date": "13 Mar, 2024",
    "Count": "188 857"
  },
...
]

I believe, it was different previously.
My suggestion would be to consider adopting a default JSON format that prioritizes raw data. For instance:

[
  {
    "Created Date": "13.03.2024", 
    "Count": 188857
  },
...
]

Alternatively, providing the option to configure JSON export formatting independently of the report formatting could be beneficial, especially since these files are often used in technical implementations where human readability is less of a concern.

Best,
Rust

2

we're discussing this internally, but the thing is: users have wanted exports to be consistent to the UI since... forever