seniordev555 opened a new issue #4070: There are some break/conflict when importing/exporting dashboard between different superset instances URL: https://github.com/apache/incubator-superset/issues/4070 We have 2 superset instances running on live production. One is for our developers to design/implement the awesome dashboards and slices, and providing them to customers. The other one is for customers to add, update and view their slices and dashboards. What we are going to do is that once we develop new slice and dashboard, we want to export these resources from developer superset and import them to customer superset without conflict. ### Superset version 0.22.0 ### Expected results We want to import dashboards and slices without any break of existing resources in running superset. ### Actual results With our research, while importing them, superset is checking the remote id. For example, there is a export file from developer superset and the other export file from customer superset. Unfortunately dashboards of these 2 export files have same remote id. If we are going to import these 2 files to customer superset, it will totally be conflict. We really want to know: 1. How can we import/export dashboards and slices from/to different superset without any break or conflict? 2. We are thinking that it is because of remote id (it is coming from original id of dashboard and slice). So what if we change all ids from id(integer) to uuid-type? If it is possible, how can we implement(customize) it? We'd like to hear good news from you soon.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
