apache/superset

Superset-4.1.1 : Not able to see download to CSV option in Superset UI.

rabindragogoi opened this issue · 6 comments

rabindragogoi commented

Bug description

In Superset-4.1.1
After running a query and getting results I am not able to find the option of download_to_csv in the SQL-Lab UI.

Screenshots/recordings

image

Superset version

master / latest-dev

Python version

3.11

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
dosubot commented

The "download to CSV" option might not be visible in the SQL-Lab UI of Superset-4.1.1 if the csv prop in the ResultSet component is set to false. This prop controls the visibility of the CSV download button and defaults to true. Additionally, ensure that the user has the necessary permissions, specifically the can_export_csv permission in the SQLLab context, to export data to CSV [1].

If these conditions are met and the button is still not visible, further investigation into the configuration or permissions may be required. It's also worth checking if there are any specific configurations that might disable the CSV export feature for the "TrinoGateway" database, although no specific information was found regarding this [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

  • 👍1
  • 👎1
michael-s-molina commented

@rabindragogoi We found a similar problem when upgrading and noticed that the SQLLab permission name was Sqllab in our database and the migrations didn't fix that. I'm assuming someone renamed the permission making some letters uppercase but didn't add a migration for it. We manually changed the name of the permission in the database.

Pinging @betodealmeida @villebro @eschutho @sadpandajoe for awareness.

sadpandajoe commented

Looking at that permissions file, there is a mix of SQLLab and SQL Lab, should we look into a migration to fix this for everyone as part of 5.0?

  • 👍1