Objects in TeamConnect can have the following types of relationships:

•Between system objects—Most system objects are associated with the History and Document system objects. The exceptions are the objects themselves, the Contact Group (Address Book) object, and Group and User account objects.

•Between system and custom objects—All custom objects are associated with certain system objects, such as Account, Appointment, Expense, Task, Document, and History objects.

•Between custom objects—You can add custom fields of type Custom Object to custom object definitions so that end users can establish relationships between custom object records. For details, see Custom Object Field Type.

•Contact-centric relationships—Certain custom objects are centered on a specific contact. For details, see Contact-Centric Custom Objects.

•Parent-child relations—Parent (or "main") objects can have multiple child objects. Each child can have only one parent object. For example, a dispute record can have multiple negotiation records, but each negotiation can have only one dispute. This type of relationship is possible between custom object definitions and between account records. For more details, see Parent-Child Relations between Custom Objects.

Parent-child relationships also exist between custom objects and their Involved objects, and between custom objects and embedded custom objects.

The following table lists objects and their default relationships in TeamConnect.

Related Object List

Points To Remember

In summary, related objects refer to:

•Child objects.

•Embedded objects

•Involved objects.

•Custom and system objects related to each other by default or through custom fields of type Custom Object.

The records of related objects can be accessed both independently from All Services (except for Involved, History, and embedded objects), and from hyperlinks, tabs, or blocks within the objects to which they are related.