Formula fields calculate results from other fields in the same record. They can handle math operations, text joining, date calculations, and conditional logic. Use them to turn repeated calculation rules into fields.
Use Cases
Data Types
Before writing a formula, confirm the types of the fields used in the calculation. Different types support different operations and functions.
Reference Fields
In a formula, reference another field by its field name. Wrap the field name in {} and keep it consistent with the actual field name:
Operators
Functions and Expressions
Common Functions
Functions perform specific operations. For example, SUM calculates a total, LEFT extracts characters from the start of text, TEXTBEFORE extracts text before a delimiter, and TEXTSPLIT splits text by a delimiter.
See the formula cheat sheet for more functions.
Text Processing
Logical Conditions
Use the IF function to return different values based on a condition:
When checking whether a field is empty, compare it with BLANK(). For example, IF({Weight}=BLANK(), 1, 2) returns 1 when a number field is empty, and 2 otherwise.
Complex Expressions
A complex formula can include multiple functions, field references, and operators. Use parentheses to control calculation order:
Result Display and Maintenance
Formula results can also use formatting and interactive display settings, such as percentage, progress bar, or icon styles. Available options depend on the formula result type.
Debugging and Optimization
- Check data types: Confirm that operations and functions use the correct data types.
- Verify field references: Confirm that field names are written correctly.
- Test step by step: Break complex formulas into smaller parts and test them separately.
- Avoid repeated calculations: If the same calculation is used in several places, consider storing the result in a separate field.
Complexity Limits
When you save a formula, Teable first expands it into the structure that actually takes part in the computation, then checks the size of that structure. If it exceeds a limit, the save is rejected and the message names what went over and the limit that applies — the number of expanded nodes, the nesting depth of the computation, the depth of references between formulas — and the change is not saved.
A short formula can still go over: when one formula references another, and that one references a third, the expanded structure grows quickly. Storing intermediate results in their own fields and cutting repeated references and complex branches usually brings it back under the limit.
If a saved formula hits a limit while computing, the field reports Formula compilation exceeds the computation limit; results have not been updated in computed field activity. Once the formula is simpler, the next write recomputes the field. Last modified on September 17, 2026
