Upgrade Plan vs update sets with record customizations

[Kristin J]

Hello!

Regarding the new Upgrade Plan feature, I would like to use it in my future upgrades/patches but I need to validate my understanding of how to handle record changes.

If I understand the scope of the Plan when it comes to capturing changes to records, it will only capture changes made to skipped records identified in the upgrade on the Builder instance. The scenario I would like to validate is:

1. On my DEV instance upgraded to Utah, I have a behaviour that is not occurring on my Tokyo Test/Prod instances
2. The affected record was not flagged as "skipped" during the upgrade process

In that scenario, what I THINK would happen is:

1. Any change I make to that record will not be captured in the Upgrade Plan because it was not flagged as skipped
2. Any change I make to any record that was not flagged as skipped will not be included in the Plan
3. Fixes to non-skipped records need to be captured in an update set
4. Update sets are promoted through my other environments as usual (once they have been upgraded to Utah with the Upgrade Plan installed)

Thanks for any info or experience you have with this. 🙂 If anyone has used the new Upgrade Plan when moving to Utah, I'd love to know how it went for you.

Cheers,
Kristin

#tokyo #upgrade #utah #upgradecenter

[koliva]

I would like to learn this as well 🙂

[Evan Miller]

I second this. The documentation is ambiguous.

[Nia McCash]

As per https://youtu.be/T13gbkrzft8?t=1633, fixes to non-skipped records still need to be captured in an update set.

I also found this video helpful for Upgrade Plans: https://www.youtube.com/watch?v=9_vo5M46dSM 

[Louis28]

Is there a Product Manager for Upgrade Plans?
There are a number of gaps that exist for this product but there doesn't seem to be anyone to bring them to.

#upgradeplans