Re-opening Update Set

[lisa_ong]

Hi guys,

Is there a way to "re-open" a completed update set? That is, once an Update Set has been completed, can the the State be changed from Completed back to In Progress.

[skendy]

Hi everyone,

I use only two instances (DEV and PROD) and I had the same doubt:

what if I wanted (because the configuration is wrong after the commit) to go back to the moment before committing an update set in PROD?

Thanks,

Skender

[alexlees]

If you view the most recently committed update in Prod, there will be a UI Action to "Back out of update set". Back out of update sets until you reach the one you wish to back out of, and then back out of this one. Order you update sets in order of 'Committed' to make this easier. Then, you can recommit the backed out of update sets which you wish to keep, but pay attention to any errors or warnings here.

Best of luck,

Alex

[skendy]

Ok. I get it Alexander. Thanks!

Only one thing:

Till now, I have transferred update sets from DEV to PROD...

Actually I have no update set (work in progress) in PROD instance (except the default one)

and nobody is working on it (I mean it is a clear/stable, already customized instance to be used by clients):

Do you suggest me to open one now and why?

Thanks a lot,

Skender

[alexlees]

What you are doing is correct - keep opening your update sets in Dev and transferring them over into Prod.

I wouldn't recommend opening an update set in Prod, nor developing directly in Prod as this will lead to untested changes going live.

[skendy]

Yes. I believe what you think.

I have read in the System Admin guide that it is not suggested to have many update sets for a few changes.

But also I do not suggest leaving an update set for a lot of time (then you do not remember all the changes developers have made).

It should be ideal thinking by 'block of changes': and giving descriptive names to update sets (depending what table or things you are developing).

Thanks for sharing your thoughts,

Skender