This section contains several examples of how to create a Linked Entities record for a number of different scenarios:
- Linked Entity Based on a Sub Type
- Linked Entity That Requires a Constraint
- Linked Entity With a Non Blank Join Table
See Figure 10.4 for an example of a basic Linked Entities record where the linked entity has a direct relationship with the current view entity.
Linked Entity Based on a Sub Type Example
An Aptify pivot table can include sub type data for the current entity. For example, as shown in, you can include Person Functions data (that is, the set of functions that are assigned to a person on the Persons record's Functions tab) in the pivot table.
Linked Sub Type Entity
In this case, the linked entity is PersonFunctions, and its PersonID field links to the Persons entity's ID field.
Linked Entity That Requires a Constraint Example
Certain entities, such as Topic Codes or Contact Logs, link to any entity using a Links entity (such as Topic Code Links or Contact Log Links). In this case, you also need to define a result constraint to filter the records in the linked entity to return the appropriate set of records.
For example, Figure 10.8 illustrates the Linked Entities record's General tab to add Topic Code Links data to a Persons pivot table.
Links Entity Relationship
In this case, the Topic Code Links entity can link to other entities in the system other than Persons (such as Companies, Products, etc.). Therefore, this record needs a Result Constraint so that it returns only records related to the Persons entity. See Figure 10.9 for the result constraint clause applicable to this situation.
Sample Result Constraint
Note that a Links entity like Topic Code Links or Contact Log Links is typically an intermediary entity that links together two other entities. In this case, you do not need to configure any Fields for this Linked Entities record since you do not want to display data from the intermediary entity in the pivot table. However, you need to create a second Linked Entities record that adds the Topic Codes or Contact Log entity to the pivot table. See "Linked Entity With a Non Blank Join Table" on page 369 for details.
Linked Entity With a Non Blank Join Table Example
To join in data from entities not directly related to the current entity, you typically need two Linked Entities record. The first record joins in the intermediary linked entity, and the second joins in the desired entity, based on its relationship with the intermediary.
For example, if you want to add Contact Log or Topic Code data to a Persons pivot table, you need two Linked Entities records. The first record joins in the Contact Log Links or Topic Code Links entity (with an applicable Result Constraint, see "Linked Entity That Requires a Constraint" on page 367 for details). The second record joins in the Contact Log or Topic Codes entity using the Links entity as its join view.
In Figure 10.10, the Topic Codes entity links to the Persons entity via the Topic Code Links entity (identified as "TCL" in the Join View field; TCL is the View Alias assigned to Topic Code Links in Figure 10.8).
Linked Entities Record with Non Blank Join View
