Relation field
Links a record with one of another entity: a task with its project, a machine
with its location, an invoice with its supplier. Instead of typing the
supplier's details again on each invoice, you take it from a list, and if its
details are corrected later, every invoice shows them corrected.
Setting it up
- Label, Required and Help text, as in any field.
- Related entity: the entity of the records the list offers. It can be the
form's own, like a task that depends on an earlier task.
- Holds: One record or Many records, like the products of a quote.
Once the form is saved, the related entity and whether it holds one or many
can't be changed.
Where it shows
- On the form, as a list with a search box. It shows records by their name
(see boards and backlogs) and, as you type, searches all of
them, even thousands. If it holds many, each one you pick is added above the
list with a button to remove it.
- In a table, with the related record's name. You can sort by it and filter
by some text it contains or by one record in particular.
- In the history, with the record's name, not a code.
- On boards and backlogs, the lanes or groups can follow this relation: one
per related record.
- On the related record, under Referenced by: there you see which
records point to it, grouped, and Add creates a new one already pointing
to it.
To show another detail of the related record, like the customer's phone, add a
formula: [customer].[phone].
Try it
There are no entities to point to here, so the list is empty.
A relation can also go inside a grid or a
dialog, where each row picks its own record, like the
product of each line of an order.
Good to know
A dialog inside another dialog can't have a relation.