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

Madhan27 · ‎02-27-2024

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

Tony Chatfield1 · ‎02-27-2024

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.

View solution in original post

Madhan27 · ‎02-27-2024

Thank you for your response @SanjivMeher , In Dev instance it was done as well with the support ticket. But how sure you are that we can delete the record in the Test instance?

SanjivMeher · ‎02-27-2024

100%...We do that every now and then. If you are sure, you fixed it in dev and test, you can safely delete the highlighted record from the update set which you will migrate to Prod.

Now if you dont want to take that route, you need another update in the same update set on the same field. Just update something in that field so that it captures the xml in the update set.

Please mark this response as correct or helpful if it assisted you with your question.

AshishKM · ‎02-27-2024

It depends on your org policy/procedures, seems like you don't have admin access on Dev instance too, controlled environment. 😎

You need to discuss with org/client authority person/lead and explain the situation and get it done [ Delete or Transfer ] via support ticket.

Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution

Madhan27 · ‎02-27-2024

I do have admin access for both the instances Test & DEv as well.

AshishKM · ‎02-27-2024

that's great, but didn't get that "why hi team is doing that change" and why you need hi ticket for such update on test.

Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution