- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 12:20 PM
I'm encountering an issue while deploying my update set. I have three fields involved: Category, Subcategory 1, and Subcategory 2. Subcategory 1 depends on Category, and Subcategory 2 depends on Subcategory 1.
In my update set, I’ve added new values to Subcategory 1 and Subcategory 2. However, in the production org, several values were added directly (not via update sets). Now, when I try to deploy my update set, I receive the following error:
"Found a local update that is newer than this one."
How can I resolve this? I need to retain both the existing values in production and the new values from my update set. Is it possible to merge the remote update into the local version without losing any data? I'd appreciate your help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 09:40 PM
this happens when the new update is already present in target instance.
If you are sure those values which were manually migrated are correct in PROD then SKIP both the errors.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
1.This is sys_choice table so the best approach here is to import the choices for particular fields to dev instance via xml from prod.
2. Make required changes like addition or deletion in an update set and them move it from dev to prod.
Raghav
MVP 2023