At some point, you've done something in a development environment that registered a change in the update set that you didn't mean to do. I've seen people just bring up a form that somehow registers a change in the current update set. What do you do with these changes that shouldn't be included in the current update set?
One way of handling this is through the use of a Recycle Bin type update set. The benefit of doing this is that it's very clear to other developers working in the system that even though the change was made, it's not intended to move anywhere or be considered.
Even though best practice is for trial and error type things to be done in a Sandbox, they can still creep into Dev through the course of development when you have lot people working on stories in two week window to get them done. Having the right containers in place for people to put these updates into will keep the environment cleaner.
To do this, you'll update the individual records in the update set to redirect them to the Recycle Bin.
Here I've added an extra field to a form that I didn't intend to keep:
After you clean up the form by removing the extra field, within the updates table, set the Update set value of the leave behind records to the Recycle Bin set.
From there, only what you want should be in your current update set.
