- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-09-2020 02:29 AM
I got an error "Found a local update that is newer than this one" while moving Update set from dev to test instance. If I accept the remote update in test will I again get the error when I move this update set to production?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-09-2020 02:35 AM
Hi,
If you accept -> the copy from your update set will get overridden in the target instance
Whether you get that error in production depends on
1) if during this update set movement it again finds a local copy which is newer then you will get it
In general if you follow the update set migration order from Dev to Test and getting this error then high chances that if you follow the same order of migration from Test to Production you will get that error
Regards
Ankur
Ankur
⨠Certified Technical Architect || ⨠9x ServiceNow MVP || ⨠ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-09-2020 02:33 AM
Hi Tapish,
If you have not moved your xml simply from test to PROD without using the update set. Then it will not give error while moving it to PROD otherwise you will receive the same error.
You can mark it as accept remote update now and it will work fine.
Please mark this answer as correct and helpful if it resolves the query and helpful alone if it lead you in right direction.
Thanks,
Mohit Kaushik
Mohit Kaushik
ServiceNow MVP (2023-2025)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-09-2020 02:35 AM
Hi,
If you accept -> the copy from your update set will get overridden in the target instance
Whether you get that error in production depends on
1) if during this update set movement it again finds a local copy which is newer then you will get it
In general if you follow the update set migration order from Dev to Test and getting this error then high chances that if you follow the same order of migration from Test to Production you will get that error
Regards
Ankur
Ankur
⨠Certified Technical Architect || ⨠9x ServiceNow MVP || ⨠ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-09-2020 02:43 AM
and If I skip it then I wont get the error again right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-09-2020 02:49 AM
That's right.
Regards
Ankur
Ankur
⨠Certified Technical Architect || ⨠9x ServiceNow MVP || ⨠ServiceNow Community Leader