- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 06:09 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2024 01:19 AM
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.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 06:16 AM
Hi @syedtufailahmed ,
The best practice would be to capture it in a update set in the lower environment & move it to higher environment. this will save your effort & time to manually go through the left ones. But lets say for some reason those are not getting captured in the update set, you can directly address them manually in the current instance.
Thanks,
Danish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 06:31 AM
Hi Danish,
Thank you for your response. I would like to know how to mitigate the below 2 scenarios,
1. If those items are already actioned in lower instance, is it still possible to capture in update set, let me know how with examples for reviewed, retained and merged?
2. If those items are not available in sys_upgrade_history_log table as skipped records then how to action them?
Regards,
Syed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 07:40 AM
Hi Danish,
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 as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 07:35 AM
Hi Danish,
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