+ Start a Discussion

What determines feature dependency in a package?

We have a package that optionally looks up campaigns and campaign members. The custom objects do not have any fields related to campaigns, nor do the S-Controls have any campaign based merge fields. An S-Control queries the campaign object, but that is contained in a Javascript string.
 When a customer tried to install our package, the installation process told him that he needed to have campaigns. What would make a package require campaigns with no explicit reference to them?
If you have a static reference to an object in your package that is flagged as a dependency by the dependency framework and can not be installed into an org that does not have that feature enabled. To find out if your package has any dependencies you can select the "Show Dependencies" button on the package or when you upload a package all of the dependencies are shown as part of the package upload process.