Dependent Units and Sub-Units

Learn about adding dependent units and sub-units to package.

In general, dependent units must be manually added to a package.

Examples: If you add a process to the package you need to manually add all required process steps as well. If you add a menu to the package, you need to explicitly add all menu actions as well.

Adding sub-units (field controls and headers) to a package:

If you add a field control or a header to a package without adding the field group/header group to which the control/header belongs, the field group/header group is not automatically created when importing the package. If the field group/header group does not exist in the target database, the subunits are not imported. The package displays "not in configuration" for those units in CRM.Designer.

In order to correctly transfer sub-units, you must own the field group/header group they belong to and explicitly add the group to the package as well.

Handling text references:

All text references used by the configuration units in the package are implicitly added and therefore automatically exported and imported with the package.

To make sure that texts implicitly contained in your package do not overwrite existing texts in the target configuration when uploading the package, you can specify a Textgroup-Name-Prefix for your package. If a prefix is defined, texts are downloaded and uploaded as a text group named <Prefix><Textgroup Name> instead of <Textgroup Name>. Thus, all text groups contained in your package gets the prefix - except text groups that were explicitly added to the package, text groups that are not part of the package configuration, and text groups that already contain this prefix.

You can also specify or change the Textgroup-Name-Prefix for imported packages: The prefix is applied when the package is uploaded.