Computed fields
Lookup, rollup, and formula fields — how each calculates its value, and worked examples.
Computed fields calculate their value automatically instead of taking direct input. All three types are read-only in the grid — Cheqq recalculates them on the server whenever the data they depend on changes.
Lookup
Pulls a single field's value through a relation, from the linked record into this one. Configure:
- Which relation field on this collection to follow.
- Which field on the target collection to pull.
Example: on a Deals collection, a "Company" lookup field that follows the Contact relation and pulls the Contact's Company field — so you can see the company on the Deals grid without opening the linked Contact.
Rollup
Aggregates a field across all records linked through a relation — useful when the relation is multiple, or even single but you want a consistent aggregation pattern. Configure:
- Which relation field to follow.
- Which field on the target collection to aggregate.
- A formula expression over the aggregated values.
Example: on a Contacts collection, a "Total pipeline" rollup field that follows the two-way Deals relation, targets each linked Deal's Amount field, and sums them.
Formula
Calculates a value from other fields on the same record, using an expression that references fields by name in curly braces: {Field Name}. The result type (text, number, date, boolean, or array) is inferred automatically when you save the formula.
Examples:
{Due Date} - {Created Time}— a "Days to close" formula computing the gap between two date fields.{Amount} * 0.1— a computed 10% commission field.IF({Stage} = "Won", "🎉", "")— a simple conditional label.
Computed fields depend on their source
A lookup or rollup field stops resolving if its relation is removed. A formula referencing a field that's later deleted will show an error until the formula is updated.
Continue with Layout types to see computed fields alongside regular ones in a Grid or as chart tiles.