Q: After writing a formula, the cell shows #REF! or similar — what’s wrong?
A: 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.Q: Why might the formula be invalid?
A: 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).
- Referenced field is deleted or missing (e.g.,
SUM([Field A])where Field A is gone).
- Percentages should be decimals in computation (10% → 0.1).
- Wrong operator usage.
- Make sure data formats are correct before sync.
Q: How do you write “not equal” in an AI Table formula?
A:!= means “not equal” in AI Table formula fields.
Q: How do you express null in an AI Table formula?
A: Use= "" directly, or use ISBLANK() to test for empty.
Q: How do you input emoji or symbols in an AI Table formula?
A:- Mac: while editing, right-click the input box, pick “Emoji & Symbols” — pick anything.
- Windows: press Win + . to open the emoji keyboard — pick anything.
Q: Can a formula field be converted to another field type?
A: Yes. Convert to text, number, multi-select, single-select, etc. Only the computed result is preserved — the field loses auto-compute.Q: How do I convert a formula field to another type?
A: 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.
Q: SUM in a formula field returns empty or errors — what happened?
A: Likely the field type doesn’t support sum. Text fields can’t sum. Convert to number first.Q: How do I adjust the format of a formula field’s return value?
A: After computation, right-click the column header → Edit field/column → pick a number format.Q: How do I change the display format of a formula field?
A: 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
Q: TEXT() output errors when used in computation — what to do?
A:TEXT() returns text. Wrap with SUM(), ABS(), etc., to convert to a number first.
Q: SUM result is wrong — why?
A: Wrong field type: only number or formula fields support sum. Convert text fields to number. Precision: too many decimals. Recompute with 4 decimal places.Q: What’s the data format of date function results?
A:- 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).
Q: Date shows as a number when concatenated to text — why?
A: Direct concat coerces date to timestamp. UseTEXT() to format as text first.
Example: [Name] & "'s birthday is " & TEXT([Birthday], "yyyy-mm-dd")
Q: Formula result should be a date but shows as a number — why?
A: Double-click the column header, set format to date.Q: How do you express “null” in a formula?
A:-
Direct check:
[Field] = "" -
Function:
ISBLANK([Field])Example:IF(ISBLANK([Date]), "Empty", "Not empty")
Q: Why does IFS() return #N/A?
A: Add a fallback TRUE.
Example:
formula
Q: How do I compute a date N working days later?
A: UseWORKDAY() — 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.
Q: Max fields a formula can reference?
A: 300 fields per formula field.Q: How to do basic per-row math?
A: Add a formula field. Reference fields and add operators directly. Example:[Field 1]+[Field 2]*[Field 3]
AI Table 2.0 formula corner
Q: A field looks like a number but I can’t do > or < on it — why?
A: Likely the formula’s output type isn’t uniform — numbers got coerced to text. Example: Field 1 formula isIF([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.
- Bad:
IF(..., [number], "text") - Good:
IF(..., [number], 0)(use 0 instead of text — keep all numbers)