> ## Documentation Index
> Fetch the complete documentation index at: https://filla.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Number, currency, and percent fields

> Numeric inputs with min/max constraints, placeholders, and an optional opinion-scale display.

## Overview

Filla supports three numeric field types that map directly to their Airtable counterparts:

| Airtable field type | Form input                         | Best for                                 |
| ------------------- | ---------------------------------- | ---------------------------------------- |
| **Number**          | Numeric input                      | Quantities, counts, scores               |
| **Currency**        | Numeric input with currency symbol | Prices, budgets, costs                   |
| **Percent**         | Numeric input with percent sign    | Rates, completion percentages, discounts |

All three share the same core settings.

## Settings reference

| Setting              | Description                                                                             |
| -------------------- | --------------------------------------------------------------------------------------- |
| **Display style**    | Choose between a standard **Number Input** and an **Opinion Scale**.                    |
| **Placeholder text** | Hint text shown when the field is empty. Supports `@` variable references.              |
| **Default value**    | Number pre-filled when the form loads.                                                  |
| **Minimum value**    | The smallest value the respondent can enter. Shows an error if the value is below this. |
| **Maximum value**    | The largest value the respondent can enter. Shows an error if the value exceeds this.   |
| **Min label**        | Opinion-scale only. Label shown under the lowest value.                                 |
| **Max label**        | Opinion-scale only. Label shown under the highest value.                                |

**Universal settings that also apply:** Label, description, required, read-only, show/hide rules, conditional read-only, reject duplicates, custom validation rules.

## Using min and max values

Min and max values enforce numeric range constraints. The form validates on blur and again on submission.

**Example uses:**

* A "Quantity" field with **Minimum value** of 1 and **Maximum value** of 100 prevents respondents from entering 0 or 500
* A "Rating" field with **Minimum value** of 1 and **Maximum value** of 10 keeps scores in range
* A "Discount percent" field with **Maximum value** of 100 prevents impossible discounts

## Opinion scale display

When you switch **Display style** to **Opinion Scale**, the field still saves a number to Airtable, but respondents answer by clicking a value on a scale instead of typing.

This is useful for:

* satisfaction scores
* recommendation likelihood
* agreement scales
* 1-to-5 or 1-to-10 evaluations

You can use **Min label** and **Max label** to anchor the ends of the scale, for example:

* `Strongly disagree` → `Strongly agree`
* `Not likely` → `Very likely`
* `Poor fit` → `Perfect fit`

## Currency and percent display

The currency symbol and percent sign are inherited from your Airtable field configuration. Filla reads them from the field's settings in your base. You configure the symbol and format in Airtable, not in Filla.

## Common questions

<AccordionGroup>
  <Accordion title="Can I accept decimal numbers?">
    Yes. Airtable number and currency fields support decimals. The form accepts decimal input as long as the Airtable field is configured to allow them.
  </Accordion>

  <Accordion title="Does opinion scale still save a number in Airtable?">
    Yes. Opinion scale is only a display style. The saved value is still numeric, so you can use it in Airtable formulas, filters, automations, and reports.
  </Accordion>

  <Accordion title="Can I use a formula for the default value?">
    Default values support `@` variable references to other form fields, not Airtable formulas. You can reference a previous field's value to pre-fill a calculation-style default.
  </Accordion>

  <Accordion title="What happens if the respondent enters text in a number field?">
    The field only accepts numeric input. Non-numeric characters are rejected immediately. The respondent cannot type letters or symbols in a number field.
  </Accordion>
</AccordionGroup>