Update set captures were not making any changes on the higher instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 11:13 AM
Hi community,
I have captures some changes on the number maintenance on a custom table and moved the update set to higher instance, And I can see the changes in the higher instance in the customer updates as well. But the configuration changes were not applying in that instance.
Customer update set XML from the higher instance.
Its not showing the prefix on the number maintenance on the higher instance.
Please help me on it.
TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 12:38 PM - edited 03-11-2024 12:39 PM
Try adding the record from the 'sys_number_counter' table, that matches the table for the sys_number record, that is in the lower instance, export it and import it in the higher instance. Since the sys_number_counter records are not captured in update sets OOB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 12:48 PM
Hi, unfortunately a partial screenshot and minimal diagnostic information does not provide the community with much with which to help you identify your issue.
Did the update preview show any errors, did the update result in any log files?
Have you compared the sys_id's of the existing sys_number record and the record in the update set?
Have you compared the updated on\by timestamps of the production record to see if they meet the update xml?
I can see no reason why an update-set would partially apply in normal circumstances and cannot reproduce this in PDI testing. Could it be that the impacted sys_number record was created manually in prod, or that there are 2 different update records as the original sys_number record was deleted in sub-prod before being recreated.
If you cannot identify a cause, then I would recommend that you log a case with ServiceNow support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 01:40 PM
Hi @Madhan27 ,
Captutre "sys_number" and "sys_number_counter" tables in update sets. Use Add to update set utility in your instance. You can capture changes in update set.
The complete step by step details on how to bring the 'Add to Update Set' utility on your PDI is given here.
Add to Update Set Utility Documentation and Custom Configurations
The simple way to enable is:
- Download the update set attached to this post
- Import it to your update set
- Navigate to Retrieved Update Sets module
- Search for Add to Update Set Global v7.7
- Preview and then commit up.
If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!
Thanks & Regards,
Sumanth Meda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 02:43 PM
I would not recommend capturing sys_number_counter updates in an update-set, as this may result in incorrect or duplicate record numbering in your production instance.