changing update set state from completed to in progess

[Hitesh targe]

Hi,

would like to understand more about update set.

what will happen if we change the update set from completed to in progress? Any issues?

Thanks

[Andras Kisgyorg]

Hi,

What I usually do is I use versioning. Once I complete an update set, and then later keep on working on the same set of functionality, I create another update set suffixed with "v2" and then "v3" etc. update sets. E.g. Portal updates v1, then create Portal updates v2, not reopening any completed ones.

This, also suggests to commit them in the proper order in the target instance. I don't merge update sets.

I do the same even if I have to touch the same configuration, again. For example, I do an update to a Business rule in an update set, I set it complete later. Then if I need to update the same business rule again, I capture it in the "v2" update set. Provided I then commit the update sets in the numbered order, I commit all the updates in the target instance same manner I made it in non-production.

What is important is NOT to move customer update records between update sets. As, by doing so, you may end up having multiple sys_update_xml records about the same target record to be in an update set. I make sure I only have a single update entry about each target name in a given update set, otherwise, I found it unpredictable which of these duplicated updates will be committed, not necessary the latest.

I hope this helps,

Best regards,

A.