function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Paul Dyson.ax812Paul Dyson.ax812 

Deploying packaged fields 'hiding' unpackaged fields

We've recently been caught out a couple of times by deployment of a package breaking page layouts and reports. Here's what seems to be happening.



  • We have a custom field called Nickname on Contact (API name Nickname__c)
  • We also have a managed package which has a field called Nickname on Contact (API name MyManagedPackage__Nickname__c)
  • We have page layouts and reports referring to Nickname__c
  • We deploy the managed package to the org
  • Nickname__c disappears from the page layouts and reports
  • On further investigation, the field level security of Nickname__c has been set so the field is no longer visible to any profile
  • Restoring the field level security fixes the page layouts and reports although the builders for each doesn't make it easy to figure out which of the two fields you're dealing with as there is no namespace qualification
Is this expected behaviour? If so what scenario is it trying to deal with and is there any way to detect it has happened. We build a product for a narrow business domain so this type of clash between our packaged field names and custom fields added to the clients org is actually reasonably common? 
Is it a bug?



This isn't expected behavior.  Can you log a case with Salesforce support and provide the steps to reproduce this?  I tried following the steps below, but was unsuccessful at reproducing the issue.