Troubleshooting
How to diagnose and fix formula fields that aren't returning the expected value in Noloco. Common pitfalls include comparing Single/Multiple Option fields against bare identifiers instead of quoted op
If your formula isn't working as expected, the most common cause is an incompatible field type. For example, trying to perform a calculation on a text field, or using a date field in a way that requires a number, will cause errors.
A frequent mistake is when fields are set up as text fields but used in a formula as if they were numbers — for instance, comparing two text values like "45" and "60" as though they were numeric. Since they're stored as text, the formula can't evaluate the comparison correctly.
Troubleshooting checklist
Check field types — confirm whether the fields in your formula are text, number, date, boolean, etc.
Match field type to operation — ensure the operation you're performing (e.g., addition, concatenation) is valid for that field type.
Adjust if needed — update the field type (for example, change from text to number) or rewrite the formula to match the data type.
Test the formula — try the formula by selecting a record and seeing if the preview result matches what you expect.
Common pitfalls
Comparing against Single / Multiple Option fields
When you compare a Single Option Select or Multiple Option Select field, the comparison value must be the option's name (its underlying value) written as a quoted string — not a bare identifier.
✅ Correct:
status = "Approved"❌ Wrong:
status = APPROVED— bare identifier; the formula treatsAPPROVEDas a missing field reference.❌ Wrong: matching against the option's display label when it differs from the underlying name — use the name, not the display value.
NULL, TRUE, and FALSE need parentheses
These are functions in Noloco formulas. They must be called with parentheses:
✅ Correct:
NULL(),TRUE(),FALSE()❌ Wrong:
NULL,TRUE,FALSE
Spreadsheet functions that don't exist in Noloco
Some common spreadsheet operators have no Noloco equivalent. See the Not supported section on the date & time operators page — most notably:
NETWORKDAYSis not supported. UseWORKDAYwhen you need a date N working days from a start date.DATEADDis not supported. Use the+operator (e.g.date + 7) orEDATEfor months.
NOW() and TODAY() don't auto-refresh
NOW() and TODAY() are supported, but they're not live values. A formula field only recalculates when its referenced fields change (or when the formula or the record is created or edited) — so a due_date - TODAY() formula will not tick down on its own each day. If you need a live "days until" or "elapsed time" value, use a runtime filter or a workflow instead of a formula field.
Related
Last updated
Was this helpful?

