Types of Errors, Causes & Solutions in Update set
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2024 01:53 AM - edited 10-16-2024 02:14 AM
Hi guys,
Most of us face common types for update set errors while previewing them. This article will help you solve some of them.
Could not find a record in sys_ui_policy for column ui_policy referenced in this update
- Type of error : Missing object
- Cause : You might get this issue as the record you are moving to another instance might have parent record that is missing on other instance.
- Solution : You need to move the parent record first then you will see this error will get resolved once you preview the old update set again.
Found a local update that is newer than this one
- Type of error : Collision
- Cause : Suppose two people are working on same script include on Dev you made some changes suppose version 1, after that other person make changes on the same after you with version 2 & he moves this changes to test instance (V2). Now if you try to commit update set with V1 after V2 is committed you will get this error.
- Solution : You will have option to accept or reject remote update check by comparing with local version if the changes you are trying to commit are already there or not.
Could not find a table field (case.reference) referenced in this update, but did find it in another uncommitted update set
- Type of error : Uncommitted update
- Cause : The object exists in another remote update set that has not been committed.
- Solution : Commit the other remote update set first or move this update to the other update set.
The table (table_name) is going to be deleted including all data. Reverting this update will not restore data.
- Type of error : Warning
- Cause : You are trying to delete a table that has data.
- Solution : If you are sure about deleting the table & all the data it contains go forward & accept remote update else skip remote update.
Could not find a record in sys_app_category for column category referenced in this update
- Type of error : Scoped Application Menu Category
- Cause : The application menu created for new custom app have no category specified
- Solution : Go to the application menu & add category as Custom Application for the new app, import the new updated update set for the application or Accept the remote update which will populate the category automatically as Custom Application.
Note : If update set contains deleted customer updates for the records, if those records are not present in the instance you should move deleted customer updates to default update set for the respective application. Don’t move default update sets.
Comment if you have faced errors apart from this with cause & solution which will help others to resolve them.
Please Mark Helpful and Correct if it really helps you.
Regards,
Mayur Shardul
ServiceNow Rising Star 2024