AgileApps Support Wiki Pre Release

Difference between revisions of "Packaging Objects in a Master-Detail relationship"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 1: Line 1:
{{Note|<br>Master-Detail relationships have been deprecated. They are no longer required, as [[Rollup Summary Fields]] achieve the same goals, and are more general.<br>This section is provided for legacy objects that have that relationship defined.}}
{{Note|<br>Master-Detail relationships have been deprecated. ([[Rollup Summary Fields]] achieve the same goals, with greater generality.)<br>This section is provided for legacy objects that have that relationship defined.}}


*If a Detail object is added to a [[Package]], the Master object is added (automatically) as a dependent object
*If a Detail object is added to a [[Package]], the Master object is added (automatically) as a dependent object

Revision as of 00:56, 16 July 2014

Notepad.png

Note:
Master-Detail relationships have been deprecated. (Rollup Summary Fields achieve the same goals, with greater generality.)
This section is provided for legacy objects that have that relationship defined.

  • 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