Update set deployment issue

[Vijay Kumar4]

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.

[Dr Atul G- LNG]

Hi @Vijay Kumar4 

I believe the issue is caused by having the same name for the category/subcategory in production. Technically, it's incorrect to create the category/subcategory values directly in production. In this case:

• delete the same category/subcategory values in both development and test environments, ensuring the system ID for the category/subcategory is consistent across all environments.

• It's better to transfer the values from production to development and test environments via XML.

• After that, bring the update set again by either changing just the dot or commenting in production, or skipping the remote update set.

[Chaitanya ILCR]

Hi @Vijay Kumar4 ,

I agree with @Dr Atul G- LNG 

in addition to that 

if the choices of Dev from where you have captured the choices are not in synch with Prod do not move the choices to prod via the update set. that will cause a lot of issues

either just follow the same approach that your organization is following today or take the XMLs of just the sys_choices that you have created and import them to prod

if you move them via update set that will move the choice set (all choices under that field) and replace all the choices in prod

here is the very good support article on choices and choice sets: 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0656146

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

[Ankur Bawiskar · Accepted solution]

@Vijay Kumar4 

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 Bawiskar]

@Vijay Kumar4 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.