Relationships

A relation links a record to one or more records in another table. It is how you connect your data instead of repeating it.

Say you track spending. You keep an Expenses table and a Categories table. Rather than typing “Groceries” on every expense, you give Expenses a relation column that points at Categories. Each expense now links to a real category record, and renaming “Groceries” once updates everywhere it is used.

Adding a relation

1. Open the table that will hold the link (here, Expenses) and tap Add field.

2. Choose Relation from the Advanced group, and give the column a name like “Category”.

3. Pick the table it references (here, Categories). This is required.

4. Decide whether to Allow multiple. Off means one link per record; on means a record can point at several.

5. Save. The column now opens a picker of records from the table you chose.

📷 Screenshot: the relation settings, with References table and Allow multiple.

Note

You can only point a relation at a table that already exists. If the picker is empty, create the other table first, then come back.

The settings

References table

The table this column links to. Records in that table become the options in the picker.

Allow multiple

Off, a record links to exactly one target (an expense has one category). On, it can link to many (a project has several team members). You can switch this later.

Display column

Linked records show as chips and picker rows. Display column decides which column of the target table is shown on those chips. Leave it on Auto and Briques picks the most readable column, usually a title or name. Set it explicitly when you would rather show, say, an order number than a title.

Filter records

An optional way to keep the picker short and correct. It scopes the options to records that match another relation on the same row.

The classic case is a chain of three tables. A Visit links to a Client and to a Project, and every project belongs to a client. Set the Project relation to filter by Client, and once you pick the client on a visit, the project picker only offers that client’s projects. No filter means the picker always shows every record in the target table.

A worked example

A simple expense tracker uses two tables:

• Categories — name (text), budget (currency).
• Expenses — title (text), amount (currency), date (date), and Category (relation to Categories, single).

With that link in place, an expense detail can show its category’s name and budget, and a category view can total the expenses that point back to it. One relation column, and the two tables work together.