With certain extremely complex Data Designer designs, it can be quite easy to ruin a dataset and underlying reports/dashboard by accidentally changing a node’s configuration. 

It would be amazing if there was a concept of versioning within Data Designer designs.

Whenever a change is made to the design, it should be in “draft” form. When you’re ready to publish that design, you commit the design by publishing a new version. If you ever need to roll back, go to the previous version.

In the current form, our CS Operations folks are generating duplicates of data designs, creating a mess of duplication to clean up, just to test out an idea on an existing design.