Problem: The auto-save feature in Gen 2 Dataflows automatically saves changes as you develop the dataflow. While generally helpful, this can be problematic in certain situations:
- Experimental Changes: When making significant changes or experimenting with different transformations, auto-save can create unwanted versions or interfere with the development process.
- Accidental Errors: If you accidentally introduce an error or break the dataflow, auto-save might save the broken state before you can revert the changes.
- Version Control: Auto-save can make it more difficult to manage versions of your dataflow, especially if you're using Git integration.
Proposed Solution: The feature request is for Microsoft to add a setting (e.g., a checkbox or toggle in the Dataflow editor) that allows users to enable or disable auto-save. When auto-save is disabled, changes would only be saved when the user explicitly clicks a "Save" button.
Benefits of Implementing this Feature:
- Improved Control: Developers would have more control over when their changes are saved.
- Reduced Risk of Errors: It would be easier to experiment with changes without the risk of auto-saving a broken state.
- Better Version Control: It would simplify version management, especially when using Git integration.
timcalil
on:
Tableau has an inbuilt functionality of ‘underlyin...
on:
Add “Column Width” Option in Specific Column Forma...
on:
Deployment Pipeline Can't Perform Comparison and W...
on:
absolutely essential !! able disable or show/hide...
We've recently delivered a new experience inside of Dataflow Gen2 with CI/CD support where you can close the editor and discard any changes that you have not saved.
Dataflow Gen2 with CI/CD support will no longer automatically save things, but it will prompt you that there are unsaved changes if you wish to close the editor without doing any save operations.