When managed packages that have components dependent on other packages are upgraded then some classes might not point to the correct version
Last updated 2017-06-10 ·Reference W-2608308 ·Reported By 7 users
When an install of a managed package that depends on other packages is performed there is an insert of the version into a table for each class that is part of the package, or for the classes being updated by the package along with package upgrades, even if there are no dependencies between source/target packages.
Assuming there is class called Util and is dependent of package B.
1. Install package A v1, ns : packagea
2. Install package B v1, ns : packageb
4. Upgrade package A to v2
- Class packagea.Util is assigned to v1 of package B
5. Upgrade package B to v2
After step 5, the assignment is not updated to version 2.
6. Try fixing the issue by upgrading package A to v2.1
[step 5] When package B is upgraded to v2, we do not update the version of Util, as it is in a different package - this is correct.
[step 6] If we attempt to upgrade package A to v2.1, we do not update the version of Util, as the code wasn't changed between v2 and v2.1.
1. Create a new version of Package A
2. Update the Util class with a minimal change
3. Install this package after upgrading "Package B" in the target org.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.