Skip to main content
When a formula is invalid or can’t be computed for the current row, an error code appears in the cell. See Formula error codes for code meanings.
Check the following:Symbol issues
  • Operators or brackets in non-English chars (e.g., Chinese quotes "" should be ""“).
  • Mismatched brackets (e.g., IF(TRUE,0,1)) has an extra closing paren).
Data issues
  • Referenced field is deleted or missing (e.g., SUM([Field A]) where Field A is gone).
Format issues
  • Percentages should be decimals in computation (10% → 0.1).
Syntax issues
  • Wrong operator usage.
Sync issues
  • Make sure data formats are correct before sync.
!= means “not equal” in AI Table formula fields.
Use = "" directly, or use ISBLANK() to test for empty.
  • Mac: while editing, right-click the input box, pick “Emoji & Symbols” — pick anything.
  • Windows: press Win + . to open the emoji keyboard — pick anything.
Yes. Convert to text, number, multi-select, single-select, etc. Only the computed result is preserved — the field loses auto-compute.
Right-click the column header → Edit field/column → in the panel, change Field type to the desired type.Notes:
  • After conversion, auto-compute is lost — only the converted field’s behavior remains.
  • Formula return values can be of various types — converted fields may not match. Be careful.
Likely the field type doesn’t support sum. Text fields can’t sum. Convert to number first.
After computation, right-click the column header → Edit field/column → pick a number format.
Double-click the column header to enter edit mode → in the Number format dropdown pick the format (integer, decimal, thousands, percent, currency, date, etc.).Supported formats:
  • Number: integer, decimal, thousands
  • Pro: percent, currency
  • Date: date format
TEXT() returns text. Wrap with SUM(), ABS(), etc., to convert to a number first.
Wrong field type: only number or formula fields support sum. Convert text fields to number.Precision: too many decimals. Recompute with 4 decimal places.
  • Storage: timestamp (e.g., 45071 = 2024-01-01).
  • Display: configurable as date in field settings — the underlying data is still a timestamp.
  • Filter: numeric logic (e.g., > 45071 means after 2024-01-01).
Direct concat coerces date to timestamp. Use TEXT() to format as text first.Example: [Name] & "'s birthday is " & TEXT([Birthday], "yyyy-mm-dd")
Double-click the column header, set format to date.
  • Direct check: [Field] = ""
  • Function: ISBLANK([Field]) Example: IF(ISBLANK([Date]), "Empty", "Not empty")
Add a fallback TRUE.Example:
formula
Use WORKDAY() — args: start date, days, optional holidays.Syntax: WORKDAY(start_date, days, [holidays_array])Examples:
  • WORKDAY("2024/11/01", 10) → 10 working days later.
  • For custom holidays, create a date array field as the param.
300 fields per formula field.
Add a formula field. Reference fields and add operators directly. Example: [Field 1]+[Field 2]*[Field 3]

​
AI Table 2.0 formula corner

Likely the formula’s output type isn’t uniform — numbers got coerced to text.Example: Field 1 formula is IF([Sales] > 0, [Sales], "No sales").
  • Issue: returns a number when the condition is true, text otherwise.
  • System behavior: to keep the column type uniform, the system coerces all values to text (number 100 becomes text “100”).
  • Consequence: when Field 2 does [Field 1] > 50, text vs number breaks the comparison — invalid or wrong result.
✅ Fix: keep both IF results the same type.
  • Bad: IF(..., [number], "text")
  • Good: IF(..., [number], 0) (use 0 instead of text — keep all numbers)