Package Items

The following platform elements can be selected for inclusion in a Package as package items. When selected, the dependent elements shown in the table are automatically included. (Things that are not dependent are shown as excluded.)

Standard Dependencies

Platform Element	Dependent Elements
Application	Includes Custom Objects Includes Web Tabs Includes Application settings Includes role-based Tab Preferences for objects Includes role-based View Preferences for objects
Objects (Custom Objects and System Objects)	Includes all customizable options Excludes Reports and Web Forms Reports can be individually selected. Reports on an object are not automatically included. Excludes data Package Data can be added, using Java classes that take care of adding records to the package and taking them out when the package is installed.
Object Data and other Data (Package Data)
Classes (includes user-created classes)
Mapping Profiles
Pages
Processes	The Business Hours Calendar used in processes. (A calendar modified by the installer is never overwritten, so installers are free to modify the calendar to suit their purposes.) Teams and Roles used in Process tasks
Reports
Roles
Sites	Includes Pages
Static Resources
Teams
Team Data Sharing Policies	Includes Teams and Roles involved Includes Child Teams if the Include Child Teams option is selected for that team
Translation Workbench	Includes localized labels and items
Web Services
Web Tabs	includes Pages, or Widgets, if available)

Special Dependencies

When the following elements are added to a package, the listed items are added as dependencies:

Team Data Sharing Policies

Roles and Teams included as dependencies

• If the Include Child Teams checkbox is enabled, the child teams of the selected teams in the Data Sharing Policy are added as dependencies

Objects in a Master-Detail relationship

Note: The "Master-Detail relationship" option on a Lookup field has been deprecated. This section is provided for legacy objects that have a Lookup field for which that option has been selected. Learn more: Master-Detail relationships If a Detail object is added to a Package, the Master object is added (automatically) as a dependent object If a Master object is added to a Package and if that Master object includes any Rollup Summary Fields, then the Detail object is added (automatically) as a dependent object When a Tenant installs a Package, the Rollup Summary Fields limit defined in Manage Tenant Capabilities is honored If the limit is exceeded, the installation process will stop and cannot proceed In order to complete the installation, delete existing Rollup Summary Fields to reduce the total number to within the defined limit After packaging, do not add or remove any Master-Detail relationships; doing so may cause unexpected results and/or loss of data