> 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/creating-formula-fields.md).

# Creating a formula field

Step-by-step guide to creating a formula field on a Noloco table.

This page covers how to add a formula field to a table. For the concept overview, see [Formulas](/data/collections/formulas.md). For ready-to-use formula patterns, see [Examples](/data/collections/formulas/examples.md).

### Steps

1. On the **Data** tab of your portal, navigate to the table you'd like to add the formula field to.
2. Add a new field and choose **Formula** as the type.
3. Enter the formula. To reference another field, select it from the dropDown menu to insert the reference at the current cursor location.

### Next steps

* Browse the [Operators reference](/data/collections/formulas/operators.md) to see what's supported.
* See [Examples](/data/collections/formulas/examples.md) for common patterns (full names, deadlines, calculations).
* If the formula isn't producing the expected value, see [Troubleshooting](/data/collections/formulas/troubleshooting.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 following URL with the `ask` and `goal` query parameters:

```
GET https://guides.noloco.io/data/collections/formulas/creating-formula-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.