Data Exported to CSV file differs from what is represented in Superset #32246
Replies: 1 comment
-
I found some similar discussions regarding CSV export formatting issues in Superset:
Currently, there isn't a direct solution documented in the repository for preserving number formatting during CSV export. However, Superset does have built-in functions for formatting numbers, such as Additionally, there have been updates in the Superset ecosystem to improve CSV export functionality, such as preventing integer columns from being coerced to floats and ensuring proper handling of NULL values [5]. These might not directly solve your issue but could be worth exploring. You might want to look into these discussions and updates to see if they offer any workarounds or insights that could help achieve the desired CSV export format. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report |
Beta Was this translation helpful? Give feedback.
-
Hello Everyone!
I'm experiencing a particular issue when exporting data from my superset (e.g. a simple table) to csv file.
I've edited number format in order to accomplish with my client requirements. So, for example, number 100000 in database is formatted as 100.000,00.
When I try to export a table, as well as a visual like cross-data, containing this number, in my csv I find the raw db data, that is 100000.
Is there any way to force Superset in order to achieve the desired outcome (100.000,00)?
Thanks,
D
Beta Was this translation helpful? Give feedback.
All reactions