> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/formulas/troubleshooting.md).

# Troubleshooting

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.

{% hint style="info" %}
**Tip:** If you intend to run numeric operations, make sure the fields are set to a number type. Double-checking and adjusting field types usually resolves the issue quickly.
{% endhint %}

### Troubleshooting checklist

1. **Check field types** — confirm whether the fields in your formula are text, number, date, boolean, etc.
2. **Match field type to operation** — ensure the operation you're performing (e.g., addition, concatenation) is valid for that field type.
3. **Adjust if needed** — update the field type (for example, change from text to number) or rewrite the formula to match the data type.
4. **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](/data/collections/field-types/single-option-select.md) or [Multiple Option Select](/data/collections/field-types/multiple-option-select.md) 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 treats `APPROVED` as 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](/data/collections/formulas/operators/date-and-time.md#not-supported) section on the date & time operators page — most notably:

* `NETWORKDAYS` is not supported. Use [`WORKDAY`](/data/collections/formulas/operators/date-and-time.md#workday) when you need a date N working days from a start date.
* `DATEADD` is not supported. Use the `+` operator (e.g. `date + 7`) or [`EDATE`](/data/collections/formulas/operators/date-and-time.md#edate) for 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

* [Formulas overview](/data/collections/formulas.md)
* [Operators reference](/data/collections/formulas/operators.md)
* [Examples](/data/collections/formulas/examples.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.noloco.io/data/collections/formulas/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.