Service Board > Service Board for Implementers > Post-Sync Configuration Tasks > About Objects, Fields, and Relationships > About Relationships
About Relationships
To define the way that objects interact with one another, you can specify relationships at the object-to-object and field-to-object levels. Some relationships are tied to standard fields that automatically link to new objects and are added by default during object creation.
Relationships can define access rights to specific objects or fields or applications, list views included in dashboards, or users assigned to Service Teams or Crews. For instance, the Crew Shift field in the Crew object has a relationship with the Shift object, so that when you click the Crew Shift field, a list of shifts appears.
You can define the following types of relationships:
• Referential: Generic one-to-many relationships (default).
• Master/Detail: One-to-many relationships that establish a tighter bond between two objects and have lifecycle and access control implications between a master record and its related detail records.
• Hierarchical: Special referential relationships in which objects have self-referencing Relationship fields. Records of the object form a hierarchy and can be navigated by using column and hierarchical views as well as table and calendar views.
• Multiple: Many-to-many relationships that are persisted in a dedicated relation table. Multiple relationships can be ordered or unordered.
You can also use JSON to define dependencies between Relationship fields within an object. Two types of dependencies are supported: requiredFor and dependsOn. The requiredFor dependency type is used to configure one-way dependence, and the current field must have a specified value for associated dependent fields to be editable. The dependsOn dependency type is used to configure cascading relationships based on one-way or two-way dependencies. One-way dependencies support edits to the current field only when the field specified in dependsOn has a value, and the optional value of the current field is filtered by the value of the field specified in dependsOn. Two-way dependencies support edits to both specified fields, When one dependent field is left blank, all options are shown by the other dependent field, and when one or both dependent fields have specified values, the options of each field are filtered by the value of the other field.
Inter-Field Dependency Parameters
Parameter
Description
requiredFor
The fields for which the current field is required. Either this parameter or dependsOn must be specified.
dependsOn
The fields upon which the current field depends. Either this parameter or requiredFor must be specified.
direction
Whether the inter-field dependency is the source or target of the named relationship. Optional. Default is source.
relationship
The full identifier of the relationship between two objects with the Relationship data type. Also used to filter optional values when dependsOn is specified. Optional.
bidirectional
Whether there is a two-way dependency between fields A and B. When field B has no value, all options appear in field A. Otherwise, options for field A are filtered based on the value of field B. Used only when dependsOn is specified. Optional.
cascade
Used with bidirectional to define whether the value of the current field must be cleared when the value of the associated dependent field changes. Used only when dependsOn is specified. Optional
For more information:
Was this helpful?