Preserve Column Order in Table CSV Export

[lilila]

I am experiencing this new issue with superset 36.

I am pretty sure in the previous versions of superset Table exported in CSV had column order preserved.
I also have trouble exporting CSV data with 'latin-1' encoding, which I did not have before

Is this possible or I am dreaming and it never worked ? :/

[issue-label-bot]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.59. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[lilila]

I come back on this issue, the problem is still not resolved with superset 37.
Here is an example :

The chart :

and the CSV export :

As you can see, the columns' order is modified and additionally the names of the columns were replaced by the variables :(

[michalgala]

I have the same issue, and it can be quite annoying for tables with many columns

[lilila]

I found out the problem (at least for the table export) comes from this line :
https://github.com/apache/incubator-superset/blob/ca9ca995109ee5251918b9df60980bffaf9b9a24/superset/viz.py#L325

The set function does not preserve the original order , I have seen this list(set( .... )) or set(gb) in many places in the viz.py file.
Is there any better way to preserve columns' order and make sure there is no duplicate?

[michalgala]

As a quick fix you could use:

sorted(list(gb + columns), key=list(gb + columns).index)
However, there might be some performance issues if you have many columns.

OR

list(dict.fromkeys(list(gb + columns)).keys())

[junlincc]

Hi Lila, our team mentioned that you have been providing valuable product feedbacks and requests in the community. I would like to invite you to join Superset new designated user panels. I couldn't find you on Slack, would you mind sharing your email with me and I can share more info with you if you are interested. Thanks! @lilila