- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 01:06 AM
Hi,
As part of a requirement, there is a need to delete certain fields from a custom table. I have captured the field deletions in and update set. On trying to migrate the update set to UAT(test environment), I am receiving the following message before committing:
I don't want any associated data to be lost after commit. Please let me know what exact changes would occur post commit, and how can I prevent potential data loss on migrating the updates.
Thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 06:29 AM
Hi @Supratik3
it behaves exactly the way you are already thinking of. Only the data of the 5 fields to be deleted is lost. Everything else remains untouched.
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 01:15 AM
it's a standard message which comes when you capture delete operation for field
It says if field is deleted then the data within that field will be gone and if you are ok with it or not.
To avoid potential loss
1) 1st create custom field to hold that data
2) use fix script to migrate the data from the old field to new field
3) then commit the update set
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 01:16 AM
Hi @Supratik3
I don't know what you have captured (accidentally) but the screenshot is just reflecting the deletion you wanted to transfer on UAT. It's just an OOTB warning that the Update Set contains operations which might lead to data loss.
And I don't understand why you "don't want any associated data to be lost after commit" while deleting fields! If you remove fields then the contained data is lost! Where else should the data exists after deleting the fields?
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 03:13 AM
Hi @Maik Skoddow ,
Thanks for the prompt reply. What I meant was that I wouldn't want complete records to be deleted/ some other issues arising on those records on migrating the update set.
For example, there might be 50 fields on the form, and if I delete 5 of those fields, then I am okay with data from just those 5 fields not appearing on the form, but not the entire record being deleted, or some other issue with the remaining fields on committing the update set. Hopefully all the records containing those 5 fields will remain as they are, minus the data present in those specific 5 fields. Could you confirm? Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2025 03:37 AM
If your update set includes delete captured for only 5 fields then data will be deleted from only those 5 fields and should not be having any impact anywhere.
It won't impact the records on which the field data is present, other fields value will be intact unless you have some script which manipulates other fields based on the field you are deleting.
You are moving this from DEV -> UAT -> Then verify what's the impact.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader