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?

Tapish Sharma
Tera Contributor

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?

1 ACCEPTED SOLUTION

Ankur Bawiskar
Tera Patron
Tera Patron

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

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

View solution in original post

5 REPLIES 5

Mohit Kaushik
Mega Sage
Mega Sage

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

Thanks,
Mohit Kaushik
ServiceNow MVP (2023-2025)

Ankur Bawiskar
Tera Patron
Tera Patron

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

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

and If I skip it then I wont get the error again right?

That's right.

Regards
Ankur

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader