What is the difference between merge update sets and update set batchingSummary🔹 Merge Update Sets Purpose: To combine multiple update sets into a single update set. When used: If you and your team have worked on different update sets but want to deliver them as one consolidated update set for migration. Useful when smaller update sets are created during development and later merged into one master update set for promotion. Result: Creates a new update set containing the updates from the selected update sets. Helps reduce the number of update sets you need to move across instances. Key Point: After merging, the original update sets remain unchanged — the merged one is just a copy/combination. 🔹 Update Set Batching Purpose: To group multiple update sets together so they can be previewed, committed, or backed out as a batch. When used: If your release consists of multiple update sets (for example, UI changes in one, business rules in another, data model changes in another) and you want to move/commit them together. Ensures that related update sets are deployed as one logical release package. Result: No new update set is created. Instead, the selected update sets are associated under a batch record. You can commit or back out all update sets in that batch together, maintaining consistency. Key Point: It’s about managing deployment order and grouping, not combining updates. ✅ Simple Analogy: Merge Update Sets = Mix all ingredients into one container. Update Set Batching = Keep ingredients in separate containers but carry them together in one basket. Related LinksMerge update sets Update set batching