Update set Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2015 06:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2015 06:24 AM
Hi Shikha,
Have a look on our wiki:
http://wiki.servicenow.com/index.php?title=Transferring_Update_Sets
Example: Found a local update that is newer than this one
Resolution:
Compare the two updates and determine which version to use. To use the version on the local instance, select Skip remote update. To use the version in the update set, select Accept remote update. Use these Available Actions to assist in problem resolution:
- Compare with local: opens the preview record, which provides a comparison of the differences between the local version and the version in the update set.
- Show local field or Show local record
- Show local update
Regards,
Sergiu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2015 06:33 AM
Hi Sergiu,
I have already read this all on wiki. The main problem is is i am not able to understand this "To use the version on the local instance, select Skip remote update. To use the version in the update set, select Accept remote update."
Still i clicked on Accept remote update (don't even know what it means), it is showing me the below page :
I don't know what to do next. even i don't know what was the error and has it gone or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2015 06:38 AM
The error is saying, "Hey, I (aka Test, aka Local) already have one of these that looks newer".
Local = The instance you're moving stuff to.
Remote = The update set you're trying to apply right now.
By clicking "Accept Remote Update" you've told Local (aka your Test instance) to ignore the version it has that it believes is newer and simply over-write with what you have in your update set.
The risk here is that you've had multiple developers touching the same object, and now you've overwritten that object with an older version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2015 07:10 AM
I really don't know what should have been done by me to resolve it.
Please guide me if you can as i have never worked with update sets.