> 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/simple-fields.md). # Simple Fields Standard field types for capturing text, numbers, dates, photos and more. ## Presentation *This category allows you to show the same information on all submissions.* ### Title The title is entered in the field label in the general options. This information is visible to the user on mobile as well as on the web. ### Static text * **Rich text:** advanced mode with some language-based formatting options [Markdown](https://fr.wikipedia.org/wiki/Markdown) * **Edit text:** allows you to enter the text that will be displayed to users (required) ### Logo * **Band type logo:** allows the image to be displayed across the entire width of the screen * **Upload:** choice of the image that will be displayed in the form (required) * **Hidden on the web form:** allows you to ensure that the image is only displayed on mobile devices. ## Data *This category allows the user to enter information, the type of which has been chosen.* {% hint style="info" %} **Value formatting cannot be customized.** For fields such as Number and Date, the way values are displayed (decimal separator, thousands separator, date order, etc.) is automatically applied based on each user's [language](/user-documentation/build/managing-users/users.md), not configured per field or form. {% endhint %} ### Text * **Rich text:** advanced mode with some language-based formatting options [Markdown](https://fr.wikipedia.org/wiki/Markdown). * **Default value:** applies the value entered in the field. * **Linked list:** allows you to offer auto-completion when the user types the first character of an element in the chosen [list](/user-documentation/build/building-forms/lists-management.md). * **Barcode scan:** allows mobile users to use the camera to scan a code that will be entered in the text field. * **External scan:** allows mobile to copy data from a Bluetooth scanner. * Texts are limited to 5,000 characters. {% hint style="info" %} **Voice input:** users can also fill this field by voice, using the native speech-to-text (dictation) feature built into the Android or iOS keyboard. This is a standard device capability, not a Daxium-Air setting. {% endhint %} ### Number * **Format**: conversion of data into a digital format. * **Minimum value:** sets a lower limit on accepted values. * **Maximum value:** sets an upper limit on accepted values. * **Default value:** applies the value entered in the field * We follow the standard [IEEE 754](https://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=4610933). The precision of the value depends on its format. For an integer, the value must be between -9223372036854775808 and 9223372036854775807, or between -2^63 and (2^63)-1. For a decimal number, the value is truncated to the first 14 significant numbers. ### Boolean (True/False) **Default value:** applies the value entered in the field. ### Date **Format:** allows you to define whether you only use the date or whether you also add the time. * **Minimum date / Maximum date:** restrict selectable dates to on-or-after / on-or-before another date-type field or date-type formula in the form. The date picker blocks any date outside this range from being picked, on web, on mobile, and offline. There is no option to enter a fixed literal date; the bound must reference a field. Date fields are saved in [Unix Timestamp](https://fr.wikipedia.org/wiki/Heure_Unix). {% hint style="info" %} **Preventing users from selecting a date in the past or in the future.** Minimum/Maximum date can only reference another field, so "today" needs its own: create a Date-type [formula](/user-documentation/build/building-forms/fields/formulas.md) field that returns the current date, e.g.: ```javascript return new Date().getTime() / 1000; ``` Set its [calculation rule](/user-documentation/build/building-forms/fields/formulas.md#calculation-rules) to **Auto refresh** so it always reflects the current date, then hide it from users in its [field permissions](/user-documentation/build/building-forms/conditions.md#field-permissions). Select this formula field as the **Minimum date** to block past dates, or as the **Maximum date** to block future dates. {% endhint %} ### Duration **Format:** min:sec:micro or min:sec ### Location This field allows you to collect an address and GPS coordinates (WGS 84 format) using Google Maps. There are three ways to fill it in: * **Pick a location from Google Maps** — select a point directly on the map. * **Enter an address** — when the submission is saved, Daxium-Air resolves the address to its GPS coordinates through the Google Maps API. * **Enter the GPS coordinates** — when you click save, Daxium-Air returns the matching address next to them through Google Maps. ### Email **Default value:** applies the value entered in the field. Email fields must comply with [RFC3696](https://tools.ietf.org/html/rfc3696) and [RFC2821](https://www.ietf.org/rfc/rfc2821.txt). ### Phone **Default value:** Choose the format of the number according to the country (by acting on the flag) and apply the value entered in the field. ### Image * **Format:** Choice of resolution to resize the image. * **Bass:** 640x480 * **Normal:** 1024x768 * **High:** 2048x1536 * **Original:** Original resolution (defined in mobile settings) - limited to 80 MB This drop-down menu allows you to choose the resolution for resizing an image taken by a mobile device. It is strongly recommended to reduce the default resolution of smartphone photos, this is very high and therefore increases the file transfer time (file size). * **Image limit:** sets the maximum number of images that can be linked to the field. * **File name:** allows you to include a name for the file. * **Default value:** pre-fills the field with an image in every new submission, for example a vehicle diagram or a floor plan that field users then annotate. Drop the image into the zone, or click the zone to browse for it. One image per field, in JPEG, PNG, GIF or TIFF format, up to 20 MB. Field users can replace or remove it in a submission. The image only applies to submissions created after the form is activated; removing it later does not change submissions that already contain it. ### File **File name:** allows you to include a name for the file * Here is the list of **authorized formats:** Image/gif, image/jpeg, image/png, image/tiff, image/x-png * Text/csv, text/plain, text/xml * Video/mpeg, video/mp4, video/x-msvideo * Application/zip, application/pdf, application/x-rar-compressed, application/x-tar, application/x-7z-compressed, application/x-zip-compressed * File size should not exceed 80 MB ### Signature **File name:** allows you to include a name for the file. The signature file is limited to 80 MB. ### List * **Linked list:** linking the field with a [list](/user-documentation/build/building-forms/lists-management.md). * **Multiple:** allows the choice of several values in the list. *The order of the selected values cannot be configured: they are displayed in their order of appearance in the list, not in selection order.* * **Display:** lets you choose which components are displayed. * **Display type on mobile:** allows you to use another mode of displaying a list on your mobile form. * **Input source (mobile only):** allows you to fill the list field by scanning a barcode. Camera scanning works on both platforms, but with different rules: iOS only scans one item, and only while the field is empty; Android allows continuous (burst) scanning on multiple-choice lists, adding each scanned item to the values already selected. The scanned code is compared with the name or the external ID of the items in the linked list, as an exact, case-insensitive match. * **Dependency on a list:** this function allows you to link several list fields to each other, in order to follow a tree structure. *This is only available on a single choice list and therefore not multiple*. * **Partial entry:** allows you to stop entering a list at a certain level of the list tree. * **Continue entry:** allows you to continue partial entry of a previous list field on the form. * **Finish entry:** allows you to complete the entry of a previous list field (going to the end of the tree structure). Lists are limited to 100,000 items. No limit on the number of items selected. ### User * **Multiple:** allows the selection of several users in the field. * **Display:** choose whether users are shown by their full name or their email. * **Restrict to group:** limits which users can be selected to the members of one chosen user group. A User field always exposes each selected user's email, first name and last name to formulas, regardless of the Display setting. See [Formulas](/user-documentation/build/building-forms/fields/formulas.md) for the value shape. Assigning an inactive user to this field is rejected, unless that user was already selected before the save. See [Submission saving rules](/user-documentation/support/admin-support/submission-saving-rules.md#field-validation) for details. {% hint style="info" %} **`separator` is not a field type.** It's a parameter name used by the `List()` and `Split()` report functions to define which character joins or splits values. See [Report syntax](/user-documentation/build/building-the-reporting/syntax-functions.md#utility-functions). {% endhint %} --- # 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/simple-fields.md?ask=&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.