+ Start a Discussion

Default namespace for custom sObjects outside of the managed package?

Is there a default namespace we can use to fully qualify a custom sObject reference from a managed package?


Take the situation where managed package code is trying to access a custom object in the installer's org, and has been given the appropriate settings under API Access restrictions. The sObject is queried with no prefix and works fine.


But if the custom object name shadows an identical object name in the managed package, the lack of namespace prefix means that the from the managed package code the system identifies the packaged object first. How do we enforce a reference to the installer's org's custom object?


In Apex code there is the System namespace leading to references such as System.Math.... but I cannot find an equivalent fully qualified reference for a custom object.