Default value of custom field not updated upon upgrade if it reference a newly added custom setting field
Last updated 2022-02-10 ·Reference W-1831676 ·Reported By 0 users
There is an issue during package upgrade, where a custom field with a default value is not updated after upgrade if the field references another newly added custom field.
1) Update the default value of a custom field included in a managed package to include a reference to another new custom field.
2) Upgrade the package in an org
None at this time.
Reported By (0)
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.