Difference between revisions of "Packaging Objects in a Master-Detail relationship"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
{{Note| Master-Detail relationships have been deprecated, as they are no longer required. ([[Rollup Summary Fields]] achieve the same goals, more easily.) This section is provided for legacy objects that have that relationship defined.}} | {{Note|<br>Master-Detail relationships have been deprecated, as they are no longer required.<br>([[Rollup Summary Fields]] achieve the same goals, more easily.)<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:55, 16 July 2014
Note:
Master-Detail relationships have been deprecated, as they are no longer required.
(Rollup Summary Fields achieve the same goals, more easily.)
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