What is the best practice to action left over skipped items

[syedtufailahmed]

Hi,

If we have skipped items left in current instance even after moving the update sets from lower instance. How to action them?

Should we again capture the same items from lower instance, or we can directly action in the current instance?

Regards,

Syed

[Venkata Mani]

Hi @syedtufailahmed,

Whenever we performed Revert to Base/Merged these records data will captured in "sys_update_xml" table.

Just need to apply filter based on requirement like who all are worked, update set name(default mostly) & when started working on skipped records.

I hope it will help your upgrade queries. 

[syedtufailahmed]

Hi @Danish Bhairag2 

Thanks for responding. I am currently stuck with below 2 scenarios, could you please advise on the same?

1. If a skipped item is already actioned in sys_upgrade_history_log table in lower environment, then how to capture in update set? Please provide an example for reviewed, retained and merged scenarios.

 2. If a skipped item is not found in sys_upgrade_history_log table then how to action/capture in update set?

Regards,

Syed

[Mark Manders · Accepted solution]

Best thing to do is to create a new update set on the 2nd environment and go through all skipped updates that weren't addressed by applying the update set from the first environment. Make the first update set the parent of the second, so you can move it as one to the next one.

For your answers: it will be captured in your new update set, since you are making a change to it after the first update set was already applied. And that goes for both of your questions.