A Lookup field propagates field values from a parent or referenced object to a child object, referring object, or document. This allows users to view relevant information from a related record. Lookup fields are never editable; they simply provide a way of displaying information from a related object record. You can search, filter, and report on lookup fields. They also allow more granularity for Dynamic Access Control. Lookup fields can exist on objects, high volume objects, or documents.
Note: Lookup fields update asynchronously. For this reason, we do not recommend using them as conditions in time-based processes such as lifecycle entry actions or entry criteria.
In Edit mode, the value of a Lookup field updates automatically when changing its parent or referenced object field.
Lookup fields on objects and high volume objects must utilize an outbound (parent or referring) object relationship:
- Example Parent-Child Relationship: Product is the parent object to Marketing Campaign. You could create a lookup field on the Marketing Campaign object which pulls data from the Product object, but you could not create a lookup field on the Product object to pull data from the Marketing Campaign object.
- Example Reference Relationship: This only applies to lookup fields on objects: The Agency object has a referring relationship pointing to the Marketing Campaign object. You could create a lookup field on Agency to pull data from Marketing Campaign, but could not create a lookup field on Marketing Campaign to pull data from the Agency object.
If the source field you use for a lookup is a reference field, the object you’re adding the field on inherits that relationship, which means that you can now use that relationship in reports and dashboards.
Lookup fields on documents must utilize an object relationship created through an object-type document field. They cannot use a relationship created through a document reference field on an object.
- Example Document-Object Relationship: The Product field on the Promotional Piece document type creates a relationship between that document type and the Product object. You could create a lookup field the document type which pulls data from the Product Family field on the Product object.
Field Types & Restrictions
When creating a lookup-type field on a document, the source field must have one of the following field types:
- Picklist (single-select and multi-select)
Objects and High Volume Objects
When creating a lookup-type field on an object or high volume object, the source field must have one of the following field types:
- Long Text
- Rich Text
A lookup field on a document can use a multi-select field as Lookup Object Field, but not as Lookup Source Field.
Lookup fields also cannot use the following as source fields:
- Fields set up in Searchable Object Fields
- Inactive fields
- Other lookup-type fields
Audit Trail Tracking
Vault adds audit trail entries on corresponding object records in the following scenarios, except for lookup-type field on a high volume object:
- The source value of a lookup field changes
- A lookup field is initialized and the lookup field value is set
- The reference object that a lookup field is based on changes
Vault adds audit trail entries corresponding to the last modified date on the record with the lookup field, which also updates under the above scenarios.
Vault limits the number of lookup fields you can create in the following ways. These limits ensure that your Vault does not experience any performance issues.
The following limits apply to lookup fields created on an object:
|Maximum Lookup field relationships||10||This is the maximum number of lookup relationships an object can have. For example, if your Product object has lookup relationships with ten (10) other objects, you will not be able to create a lookup relationship with an eleventh object.|
|Maximum Lookup fields per relationship||20||This is the maximum number of lookup fields that you can create for a lookup relationship. For example, if your Product object has a lookup relationship with the Generic Name object, you can only create 20 lookup fields on Product that reference Generic Name fields.|
|Maximum Lookup relationships to a source object||8||This is the maximum number of lookup relationships that can point to a single source object. For example, only eight (8) relationships across all objects can have a lookup relationship that references the Product object. You would not be able to create a ninth lookup relationship reference to Product from any object.|
The following limits apply to lookup-type document fields. Note that fields inherited from a higher level in the document type hierarchy count as a single field in these limit calculations.
|Lookup Fields per Object Reference Field||7||This is the maximum number of lookups that can rely on a single document-to-object reference field. For example, Product is an object reference field on Base Document. This field creates a relationship between documents and the Product object. You cannot create more than seven (7) lookup fields that use this field to point to the Product object. If a document type has two separate relationships to the same object (Product and Secondary Product), Vault calculates this limit separately for each.|
|Lookup Fields per Source Field||7||This is the maximum number of lookup fields that can point to the same source field on the source object, across the entire Vault. For example, you cannot create more than seven (7) lookup fields that get their value from the Generic Name field on the Product object.|
|Lookup Fields per Source Object||7||This is the maximum number of lookup fields that can point to any source fields on a given object, across the entire Vault. For example, Product and Secondary Product are object reference fields on Base Document, both pointing to the Product object. You cannot create more than seven (7) lookup fields that use these two document-to-object relationships because they point to the same source object (Product).|