hansabusch opened a new issue, #32644:
URL: https://github.com/apache/superset/issues/32644

   ### Bug description
   
   Problem Description:
   
   When importing a dashboard in Apache Superset and overwriting an old 
Dashboard, the system exhibits inconsistent behavior. I export a Dashboard from 
a Supersetinstance and import it to an other instance. 
   Although the versions and configurations of the Superset instances are 
identical, the following issues occur after import:
   
   Some charts are placed in the wrong tabs or outside the intended tabs.
   a random amount of Charts are duplicated: they appear both in the intended 
tab and outside, and deleting one of the duplicated charts removes both charts.
   An error message is displayed where the moved charts should be displayed: 
"There is no diagram definition associated with this component. Could it have 
been deleted? Delete this container and save to remove this message."
   Steps to Reproduce:
   
   Export a dashboard from Superset Instance 1 using the export function.
   Import the entire export folder (including YAML files) to Superset Instance 
2, overwriting the existing dashboard.
   Observe that charts are misplaced or duplicated.
   Expected Behavior:
   
   The imported dashboard should appear identical on Instance 2 as it does on 
Instance 1.
   
   Actual Behavior:
   
   Charts are not in their intended position and are partially duplicated.
   
   Environment:
   
   Superset Version: 4.0.2
   Execution Environment: Docker Container
   Connected Databases: PostGIS database version 17-3.5-alpine, internal 
Postgres database version 15
   Workaround:
   
   The issue does not occur if all existing dashboards and datasets in the 
instance are deleted before importing.
   
   Priority:
   
   Due to the existing workaround, the priority is not high, but resolving the 
issue would make the import process more efficient.
   
   Additional Information:
   
   No related issues or documentation could be found that explain this 
behavior. Currently, the only known solution is to clean the instance before 
importing.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### 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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to