The impact of namespacing Salesforce instances on the component bundle

When you namespace a Salesforce instance for managed package creation, note that when you package, your custom objects and custom fields get namespaced. For example, let's say you have an object that is named Project; the object once packaged in an Org as the SearchApp namespace has the SearchApp__Project object name. The namespace is added with double underscores for all custom object and custom fields. This allows the managed package components to be unique and not conflict with the components with the same name in the Salesforce Organization where the package is installed (subscriber Org).

 

During the packaging process, Salesforce automatically takes care of namespacing fields and objects referenced in Apex classes in the package-generation process, so you don't have to explicitly namespace the fields in the code. This allows the developers to work in any Salesforce Org and move code to the packaging Org without having...