Difference between revisions of "Package Items"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 25: Line 25:
|-
|-
|valign="top"|
|valign="top"|
*Object Data and<br>other Data<br>([[Package Data]])
*Object Data and other Data<br>([[Package Data]])
|
|


Line 55: Line 55:
|-
|-
|valign="top"|
|valign="top"|
*Web Tabs (includes [[Components]], [[Pages]], or [[Widgets]], if available)
*Web Tabs (includes [[Components]],<br>[[Pages]], or [[Widgets]], if available)
|
|



Revision as of 00:10, 29 July 2011

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
  • Classes (includes
    user-created classes)
  • Includes Teams and Roles involved
  • Includes Child Teams if the Include Child Teams option is selected for that team
  • Includes localized labels and items
  • Sites

Special Dependencies

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

Opportunity
Price Book and Product are added as dependencies
Product
Price Book is added as dependency
Price Book
Product is added as a dependency
Campaign
List and List member are added as dependencies
Lists
List member is added as a dependency
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

Notepad.png

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