Is there any issue/concern in deleting an update set that has only been previewed--NOT--committed?

[johnthomas]

I retrieved an update set from our DEV instance to our PROD instance, but I think I want to do something different than what is in this update set.   I'd like to delete this update set on PROD (again, just previewed, not committed) so that it does not accidentally get committed.

I would just clone my PROD instance to my DEV instance to ensure the update set initially done on DEV is also eliminated.

[aaronbartosch]

Should not cause any issues since it's just previewed.   Have fun deleting!

[richelle_pivec]

Not that I know of...though I don't usually delete update sets that I don't want. I would probably move the update set's State to "Backed Out."  

But I agree with you. Previewing is not Committing, so it should be fine to just move the State.

Richelle

[mikemagarino]

Hi John,

There should be no issue to delete an update set that has been previewed but not committed. None of the updates have gone through, and the only deletes that will take place are the Update Set itself as well as the accompanying records on sys_update_xml.

[saprem_d · Accepted solution]

Hi,

There is no risk of doing this as previewing just validates the scope of updates to be committed. I did it quite a few times