In Summer '19, upon package upgrade, profile permissions for child objects are not being applied
Last updated 2019-08-02 ·Reference W-6346437 ·Reported By 20 users
When a subscriber updates a package installed in their environment, if the package version being upgraded to introduces a child object that is related to a parent object which was added to the package in an earlier version, then object permissions for the child object are not applied to profiles.
This is affecting orgs on the Summer '19 release.
1. Upgrade an installed package, where the version being upgraded to has added a child object to a parent object that was added in an earlier version
2. Apply profile permissions upon upgrade
3. Observe that the child object's profile permissions are missing
Manually update profile object permissions.
Reported By (20)
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.