+ Start a Discussion

Packaging Optional Components

I am creating a managed package that will be installed on EE, UE, and embedded OEM platform edition org types.  There is optional code -- triggers, Apex classes -- that references the Opportunity standard object.  This object is not available in the embedded OEM platform product.


What happens when a customer installs my code on the OEM embedded platform?  Does it error out completely?  Or, can the installation proceed and somehow ignore the Opportunity-related code?