Custom Fields
Org-defined fields that shape the forms across FMX — what they are and where they appear.
Much of what you fill in on FMX forms isn't fixed — it's custom fields, defined by your organization's administrators. That's why two organizations' work request forms rarely look alike. Even fields that feel built-in can be custom: "Manufacturer" on an equipment item, for instance, is a custom field.
Where custom fields appear
Administrators can add fields to records like equipment items, equipment logs, inventory items, users and contacts, resources, buildings, and purchase order line items — and to each stage of a request's life. A work request module, for example, can carry separate custom fields on its details form, responses, assignment, resolution, and finalization, so the resolution form can ask questions the submission form doesn't. Work tasks add fields on instruction sets and executions, and utility providers can have fields on bill entry.
Field types
| Type | What it holds |
|---|---|
| Text | Free text, optionally multiple lines |
| Number | A number; can disallow negative values |
| Currency | A money amount |
| Date | A date; can send a notification when the date arrives |
| Time | A time of day |
| Checkbox | Yes/no — also the building block of work task checklists |
| Drop down list | A pick list of options; the only type with default values, and it can allow an "other" option or multiple selections |
| User | One or more people from your organization |
| URL | A web link |
| Attachments | File uploads |
| Read only | Display-only text — instructions on the form, not data entry |
How they behave
A custom field acts like any built-in field: it can be Required, it can show up as a grid column, in filters, and in exports (administrators control this per field, and some types are excluded — Attachments and Read only fields don't export). Bulk import templates include columns for the custom fields defined on that record type. Fields can also show or hide themselves, or calculate their own value, based on other fields — see Formula Fields.
Administrators can limit a field to certain user types, so a field may exist on a form you never see. On equipment, fields can be limited to specific Equipment types — a "Filter size" field can appear on air handlers only.
Who manages them
Creating and editing custom fields happens in Form Builder under Admin Settings, and generally requires organization administrator access. See Managing Custom Fields.
A worked example
A district wants to track filter sizes for HVAC equipment. An administrator adds a "Filter size" Text field on equipment items, limited to the "Air handler" equipment type, with Show values turned on so it appears as a grid column. Technicians see the field only on air handlers, fill it in as they service each unit, and the equipment grid becomes the district's filter-ordering list.