ITNoesis commented on issue #6197: URL: https://github.com/apache/superset/issues/6197#issuecomment-786397804
The issue is still there. When a dashboard or, slice or, table is created a unique id is assigned to it. A dashboard can easily be exported and if it is imported into another instance of superset, the import will be successful until and unless there are no tables/slices/dashboards with the same unique_id present in the target instance of superset. How I got around it? Manual pain! I exported a dashboard, edited the json and appended 100 (you need to see how many objects you have in your instance of superset/ the backend db for it) to each unique_id, imported the dashboard in same instance of superset without issues. It works but it is just a workaround not a viable solution in my opinion. The export_function should be intelligent enough to not export the unique_id and import_function should be able to assign a unique id upon import (identity column for example). Hope this helps! ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
