> For the complete documentation index, see [llms.txt](https://help.alldrafts.com/alldrafts-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alldrafts.com/alldrafts-documentation/fields/field-types.md). # Field Types #### Text Text fields are the most basic field. They render the text in the value. #### Number Number fields render their value according to the format specified. | Format | Example | | ---------------------- | --------------------- | | Digits | 100 | | Words | one hundred | | Words & Digits | one hundred (100) | | Ordinal Digits | 100th | | Ordinal Words | one hundredth | | Ordinal Words & Digits | one hundredth (100th) | #### Money Money fields take a value and an optional currency code, which can be inferred from a symbol ($ or £) or official three-letter currency code like USD, CAD, or UKP. Money fields, and specifically the dollar sign, default to US Dollars in the absence of more specific currency data. If a contract is in non-US dollars it doesn't really need to be explicit about which dollar is used as long as rendering isn't in 'Currency & Digits' format, which uses the actual currency code. All other formats render all dollars with the word dollars or the $ dollar sign.
FormatExample
Digits$1,234
Currency & DigitsUSD 1,234
Wordsone thousand two hundred and thirty-four dollars
Words with Fractionsone thousand two hundred and thirty-four and 00/100 dollars
Word with Fractions & Digitsone thousand two hundred and thirty-four and 00/100 dollars ($1,234)
#### Date Date fields work with all three of day, month, and year, and offer multiple formats for rendering, including a formal 'the' and 'this' format, e.g. this 12th day of February, 2024. #### Time Time fields accept and render time in hours and minutes on a 12-hour clock, with am/pm. #### Percent Percent fields store both percentages and basis points. (There is special handling to switch to basis points if a value is entered with 'bps' following, e.g. 12 bps vs 12%.) Internally, and for the purposes of calculations, the value of a percentage field is numerical: 12% will appear as 0.012 when used in a calculation in another field. But user input into the field is accepted in terms of % or basic points. An empty field of type Percent will parse '10' as '10%', and 0.1 as "0.1%'. #### One of \ The One of type sets a field to accept just one of preset list of values. The list of values can be specified on a single line, with each value separated by a pipe (|) character, semicolons, or commas. (Spaces around the separators will be ignored.) The multiple separators are supported for ease of use; you may find commas to be easiest for a short list, e.g. "red, blue, green", but you can use another separator when you need commas in the value, e.g. "New York, NY | Seattle, WA | Washington, D.C.". There is no format available since the field just renders as the selected value. #### Any of \ The Any of type lets the user choose one or more items from a preset list of values. The chosen items are rendered as a textual list in the form "one" or "one and two" or "one, two, and three", with a format that lets you choose whether or not the serial comma is used. #### List List fields accept a separator-based list of items which will be rendered according the specified format (for serial comma selection). A list field isn't much different than a text field for a hand-edited form, but has utility for document automation where you may want to address each list item separately. #### Person Person fields accept [Person entities](/alldrafts-documentation/person.md) from the list in the document; users can also start typing a new Person name and create the Person entity directly from the field input. #### Organization Organization fields accept [Organization entities](/alldrafts-documentation/organization.md) from the list in the document; users can also start typing a new Organization name and create the Organization entity directly the field input. #### Entity Entity is a placeholder field that will accept a Person or Organization entity, and is most commonly used in the caption or preamble when it is unknown if a party to the contract will be a person or organization. Entity subfields are the subfields common to Person and Organization entities. #### Address Used to store an address that is not associated with a Person or Organization entity (e.g. a property address in a real estate document). If there's a need for the address of a Person or Organization, it is better to create a field referring to the Address subfield of an Entity. For example, of there is a field named "Employer", and you wish to refer to the Employer's address, creating a field named "Employer.Address" is the right way to render the Employer's address, and to make sure it stays in sync if a different Person or Entity is chosen as Employer. #### Governing Law This is a special field used primarily in Venue or Governing Law clauses. It is just text, and can be filled with any text, but it has an auto-complete list to help you choose from country, state, territory, or tribal law. #### Venue Another special field that accepts any text, but auto-suggests the courts of the United States, from federal to county.