David Wagstaff on 28 Sep 2023 03:22:56
Update/change functionality when publishing Dataflow Gen2. Currently, when a dataflow is published, the dataflow is saved and then automatically runs. Dataflow Gen1 functionality never did this. When authoring all I needed to do was save the dataflow and then it could be executed whenever. Half the time I am not ready for the dataflow to run when working with Gen2 and it unnecessarily runs resulting in additional overhead for me to go clean up whatever it just did.
- Comments (2)
RE: Dataflow Gen2 Publish vs Run
I find it frustrating that I can't save changes without publishing/running the task. Most of my data processes are scheduled, and if I've already run today's task, running it again causes data duplication. I need the task to run tomorrow, but without saving the changes now, they won't be there for tomorrow.
RE: Dataflow Gen2 Publish vs Run
This is a huge regression from gen 1 dataflows. We should be able to save and publish them without triggering a run.