Update sets are a great way to move configurations between instances. However, when using update sets, there are some pitfalls that can easily be fallen into.
The main issue that most developers face is what customization will be added to an update set. Not all changes to tables are added to update sets. Whether changes to a table are added to an update set or not depends on whether the records in the table are considered data or not. Tables that are considered as data are not added to an update set; as otherwise, update sets would be filled with unnecessary records.
For example, if the incident table was included in update sets, any incidents modified or created in a development instance would be moved across to a production instance, which would not be a good idea. Most tables are included or excluded from update sets as you would expect, but some are not always obvious, so it is worth checking.
To avoid missing updates in our update sets or including updates we do not...