Hi Buddy,
This one trips a lot of people up 🙂
What ServiceNow is telling you is that the update set contains a catalog item that already exists in your instance, and your local version is newer than the one in the update set. Because of that, ServiceNow won’t let you commit until you decide what to do with that record.
To fix it, go to the Update Set Preview Problems section and look at the catalog item error. From there, you have a few options:
Compare with local – this is usually the best first step if you’re not sure. It shows you exactly what’s different between the update set and your instance.
Skip remote update – this is the most common and safest option. It tells ServiceNow to ignore that catalog item from the update set and keep your local (newer) version.
Accept remote update – only use this if you want the version from the update set and are okay overwriting your local changes.
In most cases, especially for catalog items, you’ll want to Skip remote update, then click Run Preview Again. Once there are no remaining problems, you’ll be able to commit the update set.
Basically, ServiceNow just wants you to confirm which version should win before it moves forward.
@ToyosiB - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂
