+ Start a Discussion
paul-lmipaul-lmi 

Bug when installing apps

If the target org has custom fields that are named the same as the fields included in the package, the FLS will be removed from those fields when the app is installed.  I thought the whole point of namespacing fields, objects, etc, was to ensure no conflicts or issues would arise in the existing target org's configuration.  

 

To reproduce

 

Create a field in both the development and subscriber orgs (managed package).  Install the managed packaged in the subscriber org.  The field level security configured on the subscriber's "copy" of the original, non-namespace/package field will be completely removed.

Ispita_NavatarIspita_Navatar

No it doesn't work that way -If the target org has custom fields that are named the same as the fields included in the package, the FLS will be removed from those fields when the app is installed

 

Your field s will not be removed they are different as they are prefixed with your namespace.

Hope this helps.

paul-lmipaul-lmi

This is silly.  There's zero reason for the FLS to be removed from existing custom fields.  All it does is cause support issues for the publishing org if they happen to have named something the same as the subscriber.