- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 05:43 AM
Hello,
I have made some changes to the dev instance, marked the update set as completes, and wanted to push it to the test instance.
an error has occurred while reviewing the update set caused by a change that has been made and pushed.
i want to remove the change that causes the error from my update set, what is the best practice since it is already completed ?
thank you
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 05:46 AM
Hi there,
You can ignore the remote update, which would remove it from the retrieved update set, and then you can commit the update set.
If you are working from for example DEV > TEST > ACCEPTANCE > PRODUCTION, then this also goes well when retrieving on acceptance.
If you are working from DEV > TEST, DEV > ACCEPTANCE, DEV > PRODUCTION, then you will face the same error on every instance. In that case, I would not ignore the remote update, instead delete the retrieved update set, remove the specific customer update from your update set on DEV, and retrieve again.
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 05:44 AM
In the Preview Error, you will have an option to Skip the remote update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 06:11 AM
i did that but when i do (review again) that give the same error

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 06:48 AM
Thats the expected behavior when you are doing preview again.
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 05:46 AM
Hi there,
You can ignore the remote update, which would remove it from the retrieved update set, and then you can commit the update set.
If you are working from for example DEV > TEST > ACCEPTANCE > PRODUCTION, then this also goes well when retrieving on acceptance.
If you are working from DEV > TEST, DEV > ACCEPTANCE, DEV > PRODUCTION, then you will face the same error on every instance. In that case, I would not ignore the remote update, instead delete the retrieved update set, remove the specific customer update from your update set on DEV, and retrieve again.
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field