> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/build/building-forms/fields.md).

# Fields

Learn about the different field types available in the Daxium-Air form builder.

Fields are the building blocks of your forms. Daxium-Air offers a wide range of field types to capture any kind of data.

**Presentation fields** display static content to all users on every submission — titles, text blocks and logos. Covered in [Simple Fields](/user-documentation/build/building-forms/fields/simple-fields.md).

**Data fields** capture user input: text, numbers, dates, durations, locations, emails, phone numbers, photos, files, signatures, list and user selections. Also covered in [Simple Fields](/user-documentation/build/building-forms/fields/simple-fields.md).

**Formulas** are calculated fields that derive a value from other fields using JavaScript. See [Formulas](/user-documentation/build/building-forms/fields/formulas.md).

**Relations** link submissions across forms, enabling parent-child structures and sub-forms. See [Relations](/user-documentation/build/building-forms/fields/relations.md).

**Field options** add extra behaviors to individual fields — pre-filling, advanced search and OCR recognition. See [Field Options](/user-documentation/build/building-forms/field-options.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.center.daxium-air.com/user-documentation/build/building-forms/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 `automate deployments from our CI pipeline` 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.