What is the current behavior? How do you reproduce it?
Currently using the Chrome extension, version 2.2.2. By using "Show All Fields" command on a form, all fields get marked dirty as well. Saving the form after showing all fields erroneously triggers plugins and flows that have filter criteria different than the fields that are actually changed.
What is the expected behavior?
Clicking "Show All Fields" should not set fields to dirty if they are not changed. Perhaps before setting the field visibility, the dirty-ness of the field can be tracked and set accordingly after the visibility change.
Please tell us about your environment:**
Chrome, using the 2.2.2 version of the Toolbox. Latest version of Dynamics (2020 Release wave 1; 9.1.0000.2251).
Other information
End-user here complained about this problem describing it as such: they have a flow that triggers on a field that is not visible by default. They used Show All Fields, updated a different field, and then hit save. The flow was still triggered although the field that's supposed to trigger it was not actually changed. Unfortunately, flows still do not have support for pre/post-image type comparisons, so it's not possible to just add a condition to the flow to check before/after for non-updates.