ey3ball commented on issue #22127: URL: https://github.com/apache/superset/issues/22127#issuecomment-1316840505
I'm running into this as well (superset 2.0.0) by using the import / export feature from the UI. The example given by @cleslie is about removing a chart, but the same things happens for updates : 1. Export Dashboard through the UI with chartA, datasetA 2. Modify dashboard, chartA, datasetA 3. Import back dashboard file obtained in step 1, OVERWRITE is specified in the UI 4. Dashboard configuration is rolled back, chartA and datasetA are left in their state after (2) Manually extracting datasets / charts from the archive, and importing them through the dedicated dataset / chart import tools applies updates as expected I would add it may be interesting to give the user a chance to select what actually gets updated. For my specific use case I would like charts / datasets to be updated as dependencies of the dashboard, but I need databases to remain untouched (dashboards are moved between staging / production environements which use different source databases) -- 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]
