Need clarification on the unique key for a field for migrating the update sets

[Madhan27]

Hi community,

I need some clarification on movement of my update sets. I have some unwanted records in my update sets and I don't want to migrate those to my upper environments like Stage and production. 

1. The highlighted field unique was "false", But it was captured as "True" in my update set and moved to my Test instance. As its a unique key we cant modify the changes on the field. The work arounds which I have in my mind was to delete the field entirely from the table and recreate it and capture the unique key field as "true". But by creating a new field the sysID will be different will it impact in the background? And is this the correct practice? 

2. The below following record is from the committed update set from my TEST instance with the Unique value as "True", I have changed the value as "false" by change request with serviceNow portal HI Ticket. But now I don't want to move the highlighted record to upper environment. Can I delete the highlighted record ?? If I can will it impact anything is this is the correct practice??

I need help and suggestions for the above issue.

TIA

#DevelopersForum

[Madhan27]

As we cant change the the value of the unique key, We need to drop the indexes of the field in the back end which only HI team will be having access, they will change it as per the request. 

[Tony Chatfield1 · Accepted solution]

Him if the update set is deployed to another sub-prod instance  you can still remove updates (before moving the update to prod) by opening the Customer updates tab in a new window (table sys_update_xml).
From there make sure the 'Update set' field is visible in the list.
You can then change the update-set of individual entries from the list view, just move the individual updates involved to the 'default' set for the application scope involved.