superset icon indicating copy to clipboard operation
superset copied to clipboard

Dashboard Import Error: An error occurred while importing dashboard: Error importing dashboard Please re-export your file and try importing again superset

Open praveenamdas opened this issue 9 months ago • 4 comments

I exported my dashboard from superset. I deleted it and while trying to import it again, an error pops up "An error occurred while importing dashboard: Error importing dashboard Please re-export your file and try importing again superset" I also tried importing it to another system, then also the same error ocurred. But when I import a dashboard that is exported from a different system, it works.

How to reproduce the bug

It is a first time experience. Happens in my superset.

Expected results

Import Succesful

Actual results

Couldn't import. Error occurs. An error occurred while importing dashboard: Error importing dashboard Please re-export your file and try importing again superset

Screenshots

Screenshot from 2023-11-15 16-15-27

Environment

(please complete the following information):

  • browser type and version: google - Version 114.0.5735.198 (Official Build) (64-bit)
  • superset version: 2.0.0.

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • [ ] I have reproduced the issue with at least the latest released version of superset.
  • [x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

praveenamdas avatar Nov 15 '23 10:11 praveenamdas

Please don't double-post your question https://github.com/apache/superset/discussions/25987

sebastianliebscher avatar Nov 15 '23 12:11 sebastianliebscher

I am facing same issue , is there any resolution for this ?

Satish-Pnatics avatar Dec 18 '23 06:12 Satish-Pnatics

Closing this out since it's gone silent, and we no longer support 2.0 (or 3.0). If you're facing this in 3.1/4.0, we can revisit. I suspect it's something to do with these older versions needing the VERSIONED_EXPORT feature flag turned on.

rusackas avatar Apr 18 '24 22:04 rusackas

@rusackas i face the same issue in 4.0.0

marituhone avatar Apr 25 '24 05:04 marituhone