Difference between revisions of "Packaging Objects in a Master-Detail relationship"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Note|<br>Master-Detail | {{Note|<br>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.<br>''Learn more:'' [[Master-Detail relationship]]s}} | ||
*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 | ||
Latest revision as of 21:20, 18 July 2014
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