Documentation Center

Dependency types

A dependency is absolute when the dependency always applies or occasional when the dependency sometimes applies. However, if an occasional dependency applies to an item, it must, as a rule, be transferred (or be present on the destination Content Manager).

For example, a Component must have a Schema to define its structure so it is an absolute dependency, but a Folder may have a linked Schema associated with it (in which case the linked Schema will be transferred) so the dependency is occasional (but its transfer is not optional).

Absolute dependencies
The following diagram shows the absolute dependencies between types of Content Manager items. Each item depends on the items pointing to it. For example, a Root Structure Group depends on its Publication.
Occasional dependencies

The following table shows the occasional dependencies between item types. Note that while the dependency may or may not be present, if it is present, the dependent item must be transferred, or already present on the destination Content Manager.

For example, not every Folder has a Metadata Schema, but a Folder that has a Metadata Schema depends on that Metadata Schema and must either be included in the transfer or found on the destination Content Manager, just like an absolute dependency.

An item of type......may need an item of type
PublicationMetadata Schema
PublicationComponent (linked)
PublicationProcess Definition
PublicationParent Publication
PublicationTemplate Bundle Process Definition
PublicationTask Process Definition
Target GroupTarget Group (used)
Target GroupKeyword (used)
FolderSchema (linked)
FolderMetadata Schema
Structure GroupMetadata Schema
Structure GroupComponent (linked, if the Metadata Schema uses Component Links)
Structure GroupPage Bundle Process Definition
SchemaSchema (embedded)
SchemaCategory (referenced)
SchemaSchema (referenced)
SchemaComponent (linked, as a default field value)
SchemaKeyword (as a default field value)
SchemaBundle Process Definition
ComponentComponent (linked, either in data or in metadata)
ComponentCategory (if the Metadata Schema uses Categories Links).
ComponentKeyword (used for pick values in a list)
Multimedia ComponentComponent (linked, in metadata)
Multimedia ComponentMultimedia Type
Template Building BlockTemplate Building Block (included)
Template Building BlockParameter Schema
Template Building BlockMetadata Schema
Component TemplateSchema (related)
Component TemplateCategory (tracked)
Component TemplateTemplate Building Block (included)
Page TemplateParameter Schema
Page TemplateMetadata Schema
Page TemplateTemplate Building Block (included)
Page TemplateRegion Schema (here also called Page Schema)
Region SchemaRegion Schema (for its nested Regions)
PagePage Template
PageMetadata Schema
PageComponent (linked)
PageComponent (in Component Presentation)
PageComponent Template (in Component Presentation)
PageTarget Group (in Component Presentation)
CategoryCategory (its parent Category)
CategoryMetadata Schema
KeywordKeyword (its parent Keyword)
KeywordKeyword (its related Keyword)
KeywordMetadata Schema (as of SDL Tridion 2009)
Virtual FolderMetadata Schema
Virtual FolderVirtual Folder configuration (any item)
Process DefinitionUser Group
Process DefinitionApproval Status
Process DefinitionTemplate Building Block (as of SDL Content Porter 2013)
GroupGroup Membership
GroupPublication (allowed)
Business Process TypeBundle Schema
Business Process TypeMetadata Schema

In addition to this, there are certain connections between items that could be considered occasional dependencies, but that will not cause the dependent item to be transferred or searched for on the destination Content Manager. Such connections are:

  • A Group may have a scope that limits its use to three Publications (and so is, strictly speaking, dependent on those Publications), but only two of those Publications are present on the destination Content Manager. In this situation, the scope of the Group will be updated during import.
  • An item may have application data associated with it that links to other items (and so, indirectly, the item may said to be dependent on those items). If the import is configured to not import such application data (because the application to which the application data belongs is not set up on the destination Content Manager), then this indirect dependency is also ignored.