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

AshishKM · ‎02-27-2024

Hi @Madhan27 ,

You don't need to hard delete any record ( as per screen shot ). As you have 3 instances dev->test->prod.

1)As you already committed that update set on Test but don't want single record to move on PROD, you can transfer that single record from that update set to some other update set on Test instance.

2) You should write new update set [on dev and promote to test] to correct that change on test instance , instead of direct update on test via ServiceNow Support team, are you not an admin on test instance.

Let me know if you can transfer that single item on Test instance to avoid commit on prod.

-Thanks,
AshishKM

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

Thank you for your response @AshishKM , I didn't get your 2nd point. You want me to capture the change in a different update set and what you want me to do with that?

AshishKM · ‎02-27-2024

My point 2 was "in response" of your point 2

I though you changed the value "false" direct on test instance via Hi ticket.

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??

If that was the case, then your Dev & Test both were not in sync for that record.

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

SanjivMeher · ‎02-27-2024

If you dont want to migrate to upper environment, you can delete it from update set. It is safe to do so, Since you already fixed it in Test Instance. I would also suggest creating a support request to get it fixed in Dev instance, so that in future, it is not migrated by mistake.

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