Best way to deploy update sets to Production to avoid errors

[Meet Mewada]

Hi,

I would like to know the steps, dependencies and best way to prepare the Prod instance.

We will use Update sources to move the update sets and need to understand how to avoid any kind of errors while previewing them.

Thanks,

Meet M

[-O-]

Most of the problems that are raised when previewing update sets cannot be prevented in the final step - when committing in Prod.

E.g. if people modify production directly, there is no way to prevent a conflict if the same thing has been modified in Dev too and is included in the update set to be committed.

Or, if someone committed an artifact in Prod that is actually of a newer version of the same thing being committed by the currently previewed update set, there is nothing you can do just withing the bounds of committing the update set in Prod.

For best results one should have a solid Dev to Prod process that everybody follows.

In other words the success of committing in Prod depends on starting the process correctly in Dev.

One thing that can help a bit is to commit in batches.

Remove all retrieved update sets, retrieve again, batch up all update sets to be committed preview and pray.

But really this only helps in not needing to worry about the order of update sets to be committed that time.

So, just like with health, the best bet is to prevent (follow good dev-to-prod process) and not to hope to cure (hope to fix errors before committing in prod).

[Siva Jyothi M]

Hi @Meet Mewada,

You can see the problems in the update set once you preview it. It depends on your use case whether to Accept or skip the remote update. 

If you need the version of local instance- then select Skip remote update. Because we don't need the change which is coming via update set.

If you need the version in the update set-> then select Accept remote update, this will consume the change captured in the update set.

Below actions help to identify the problem:

• Compare with local: opens the preview record, which provides a comparison of the differences between the local version and the version in the Update Set.
• Show local field or Show local record
• Show local update

Please mark this answer as correct and helpful if it solves your issue.

Regards,

Siva Jyothi M.

[Christian_]

Hello,

Batch Update set is a great feature to ease the Production deploy, as you can preview and commit them in bulk.

See Update set batching for more information on this.