The relational field allows you to build relationships between other sets of data inside GraceBlocks. For example, if you track candidates on one tab and the talent pipelines for how you want to organize the candidates on another tab, you can use the relational field to assign candidates to one or more talent pipelines. This concept allows support for database relationships inside your Blocks. To build a connection between tabs, a builder chooses the relational field type when managing fields.
This article reviews the properties of relational fields and provides tips to aid in user adoption of relational fields.
Properties of relational fields
After you specify a Field name (which controls how this field is referenced inside the tab) and that the Field type is Relational, the screen updates to display required attributes that you must define, as well as More field attributes that you can select:
This is the Block where the tab exists for which you'd like to establish the relationship. If you are working inside a Zone on the free plan, only the current Block is available. However, paid plans allow you to establish relationships with any Block inside the Zone.
|Relational tab||When you have a Block selected, you can see a list of tabs that are inside that Block. Select the tab that contains the related data you want to work with.|
If you'd like to be able to select multiple values, leave this option enabled. (It is enabled by default.) If you want to limit users to a single value selection, disable the multi-select option by toggling this option into the off position.
In our example, a candidate can belong to multiple pipelines, so the multi-select option remains on.
If a candidate should only ever only belong to one pipeline, this option would be disabled. (But if that were the case, the candidate would not have many options for where they might fit in our organization!)
When you create a relational field, you are actually creating two fields: the one where you are currently working and a companion field in the tab you are relating to. Therefore, any values selected can be seen from either record. This option determines whether the companion field is also multi-select.
In our example, each pipeline can have multiple candidates associated, so the mutli-select option remains on.
If we only ever wanted one candidate to be associated with each pipeline record, this option would be disabled. (But then we'd not have a very healthy pipeline of candidates!)
If you enter any text into the Field callout textbox, the information (i) icon appears to the left of the field name, and the text you entered displays when users move the cursor over this icon. Enter text here if you want to provide information to help the user learn more about how to use the field.
🔔 The Multi-select here and Multi-select there options require planning. The data you are working with determines whether you should turn those options on or off. You need to think carefully about how you want this to work every time you add a relational field to ensure that you choose the right option for that specific business scenario.
🔔It is NOT possible to convert a relational field into another field type later. If the field is no longer needed, you can delete it.
🔔 Once you create a relational field type, editing options for the field are limited; you can change only the following:
- Field name
- Multiselect here and Multiselect there options
- Field callout
🔔 Whether a relational field has the multi-select or single-select attribute enabled has a big impact on how it will display to the user on the details page. Understanding this layout impact can help you choose the best attributes for the data you are working with.
Single-select records are configured into the layout on the left panel, while related records will appear on the right side under Related Records. In either case, you can drill to the related record by clicking on it.