Best practices for Handling Errors while moving Update sets.

[Krishna73]

Hello Everyone,

Is there any way to find out all error handlings (Commit/Skip update) done while moving update sets from one instance to another instance ?

My situation is this - I need to move all update sets from UAT to PROD, but I dont have error handling details. Please suggest the best way to handle this situation.

Thanks

[asifnoor]

Hi,

Here are few steps that you can follow.

1. Ensure all the update sets associated to each feature are merged and have single update set per feature

2. Have the list of features that you want to deploy in a release.

3. Have the list of update sets that are developed in the same order so that commit of 1 update set does not overwrite the other or misses the dependent feature

4. Preview the update set before committing, ensure no errors. If any errors, do not commit.. fix it in your UAT, push to new update set, do the merge again and then preview the update set again.

Ref: https://old.wiki/index.php/Update_Sets_Best_Practices

https://www.oreilly.com/library/view/mastering-servicenow-scripting/9781788627092/04c2e007-eab5-497d...

Mark the comment as a correct answer and also helpful if it has answered your question.

[asifnoor]

Hello Krishna,

Kindly mark the comment as a correct answer if this has answered your question. This would remove the question form the unsolved list and others looking for similar solution can be benefitted from this.

[Ankur Bawiskar]

Hi Krishna,

It depends on your use-case whether to Accept or Skip the remote update.

Review those conflicts and that will help you decide weather to commit or skip it. That is only best practice.

For every error you get you need to analyze whether you need to Accept or Skip by comparing the versions.

For warnings you usually Accept the remote update

You can fix it by comparing the two versions and find out which one is needed.

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

You can refer this link to know how to address other type of update set transfer issues. Resolve a preview problem with an Update Set

Regards
Ankur

[Ankur Bawiskar]

Hi Krishna,

Refer below links for help

5 ServiceNow® Update Set Errors And How to Get Around Them

UPDATE SETS SUPER GUIDE

Regards
Ankur