Forum Discussion
This dataflow auto-save is killing me
How do we manage this?
- no clone
- no undo
- no close without saving
A mistake by a junior person (or even senior).... With no clone, we can't even determine what changed so we can put it back.
If we make a mistake (or even think we may have), we have to find our documentation on the feature & determine if it's doing what we want.
We need clone
We need either undo or close without saving (prefereably both)
Hi Mike,
I've passed this feedback to the PG. I'd highly recommend also posting your feedback and your main ideas about cloning or undo in the Fabric Ideas Portal --> https://aka.ms/FabricIdeas
At the moment what you can do is use the Export Template feature to create another dataflow for testing and then move those changes over to your other dataflow once you're finished. You can also check the .json file of your Dataflow to see the published version of your Dataflow which is not necessarily the same as the draft version
1 Reply
Hi Mike,
I've passed this feedback to the PG. I'd highly recommend also posting your feedback and your main ideas about cloning or undo in the Fabric Ideas Portal --> https://aka.ms/FabricIdeas
At the moment what you can do is use the Export Template feature to create another dataflow for testing and then move those changes over to your other dataflow once you're finished. You can also check the .json file of your Dataflow to see the published version of your Dataflow which is not necessarily the same as the draft version