Data type referenceReference
Relation. Put relation in the Data type column and name the target in the Value column — [Form].field, [Form].{Section}.field, or in plain English field in Form; the form name may be wrapped in brackets or quotes. The picker lists that form's records (the key plus a couple of recognizable columns). After you pick one, it offers a choice: reference only, prefill the matching header fields, or — on a form that has line items — prefill the header and the record's line items too. The referenced field must be a key or a subkey; if it's neither, the app still builds but the field stays a plain input (you'll see a warning). A relation to a subkey is scoped by the target form's key: this form must have a same-named key field (e.g. Year) filled in first, and the picker then lists only the records under that value — blank, and it asks you to fill the key field first.
2 · Standard lists. These data types come with a predefined list of standard values — they bind the field to a built-in list (no List_ sheet needed). The field becomes a searchable dropdown that stores the standard code and shows code + name. For countries, currencies and languages the name appears in the viewer's language; the stored code never changes.
| Type | Predefined standard list | Example |
|---|---|---|
| country | ISO 3166-1 countries (249) | US · United States |
| state | US states + DC & territories (57) | CA · California |
| county | US counties · FIPS (3,222) — narrows by state | 01001 · Autauga County |
| currency code | ISO 4217 currency codes (178) | USD · US Dollar |
| uom | Units of measure · UNECE Rec 20 (48) | KGM · Kilogram |
| language | ISO 639-1 languages (184) | en · English |
| timezone | IANA time zones (433) | America/Chicago |
| sex | ISO/IEC 5218 value set | Female |
| gender | Inclusive options (W3C guidance) | Non-binary |
A field merely named like one of these (gender, ship_country, …) defaults to its standard list automatically; a Rules-sheet Data type or a matching List_ sheet overrides the default.
3 · Locale-dependent types. Some types are displayed according to a region or country rather than a fixed US format. (None of these are standard lists — but the country and currency code standard lists pair naturally with them.)
| Type | Depends on | Shown as |
|---|---|---|
| number | Your region | 1,234.56 (US) · 1.234,56 (DE) |
| currency | Your region + app currency | Locale grouping & symbol; 0-decimal for ¥ / ₩ |
| percent | Your region | 15 → “15%” |
| date | Your region | MM/DD/YYYY (US) · DD/MM/YYYY (UK) |
| postal_code | The field’s country | ZIP (US) · Postcode (UK) · PIN (IN) |
| national_id | The field’s country (masked) | SSN (US) · NI no. (UK) · CPF (BR) |
| bank_id | The field’s country | Routing (US) · IBAN (EU) · Sort code (UK) |
| phone | Country calling code | +1 / +44 / +91 prefix |
postal_code, national_id, bank_id) follow the field's country (declare it on the Rules sheet), defaulting to the app's Regional defaults country (Display settings), else your region. The US-specific zip, ssn and routing_number types still work unchanged.A full reference spreadsheet ships at docs/SheetApps_Data_Types.xlsx — one tab per group above (Data Types · Standard Lists · Locale-dependent Types).