-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dashboard] Impossible to edit imported dashboard data #12495
Comments
Seems to be working just fine in newer versions, at least with the VERSIONED_EXPORTS flag enabled. Calling this one complete, but happy to re-open if anyone sees reason. |
I've had the same problem with Superset 2.0.1-dev in my production environment. Tried to investigate everything, from YAML files to backend, and couldn't explain why only imported dashboards don't allow editing, although they have the slices right. |
I am facing the same issue, using Superset Version: 2.0.1 |
For anyone looking into this, the solution we found was:
metadata:
color_scheme_domain: [] If you remove find /path/to/folder -name "*.yaml" -type f -exec sed -i '/color_scheme_domain: \[\]/d' {} \; |
I think it might be reasonable to strip |
When user exports and then imports a dashboard, it is impossible to change some data, i.e. name of the imported dashboard or name of the filter.
Expected results
It should be possible to edit data of the imported dashboard, the same as it is possible to edit data of the existing dashboard (the one user exports).
Actual results
When user changes some data, it is not presented.
In case of changing the name in all dashboard panel, it is not possible to click "save" in editing modal.
Screenshots
Change name of the imported dashboard
Change filter name of the imported dashboard
How to reproduce the bug
Environment
Last commit: #407b194b15
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
I have noticed, that if I remove last lines from JSON metadata, editing works fine.
The text was updated successfully, but these errors were encountered: