Update sets

[ad14]

I have a question about update sets. We have multiple update sets in our instance and we want to move it to prod. But the problem is for some rules like business rules , client scripts the same rule is modified in multiple update sets and it has multiple versions associated with it. How do I deal with it? I know batch update sets could be used. So do I just use batch update sets and commit the update sets in the order when they were last updated?  And FYI there are multiple update sets including parent, child, batch update sets in our instance.

[ad14]

Like how do I make sure that latest version of the update is considered for each rule when they have been modified in multiple update sets

[jonsan09]

I would definitively recommend using batch update sets if you have multiple update sets that touch the same artifact. You would add your update sets to a batch update set prior to moving to the next instance. When you are ready to move to the next instance, you'd complete the parent batch and push/commit it. The latest version of the artifact wins, when modified by different update sets in the batch. Here a good resource on best practices when using batching: https://sn-nerd.com/2023/06/13/everything-you-need-to-know-about-using-update-sets/

[ad14]

So in batch update sets when I preview and commit the parent batch update set in prod it automatically checks which version of the rule is latest and update the latest version automatically? 

[Ankur Bawiskar]

@ad14 

you can use batching for this scenario.

Update set batching 

If my response helped please mark it correct and close the thread so that it benefits future readers.