+ Start a Discussion

Field-Level Security not being set on managed package update

We believe this is a bug with Field-Level Security within managed package updates.

Steps to reproduce:
Install a managed package that has a managed object without a managed Type__c field (namespaced).
Create your own Type__c field (not namespaced) on that managed object.
Install a new version of the same managed package that contains a Type__c field (namespaced) on the same managed object - make sure to select "Grant access to all users" on the security step. This is supposed to give full access to all new components, including new fields.
See that FLS is not set for the managed Type__c field.
Best Answer chosen by trmp
In case anyone was wondering about this, here is the Known Issue: