Custom fields
Add your own fields to our records. If you take a payment somewhere else, put its reference on the invoice rather than in the notes, where nothing can find it again.
New field
| Field | On | Type | Shows up in | Filled in |
|---|---|---|---|---|
| Warranty registered with the manufacturer*Internalwarranty_registeredUnregistered equipment loses years of parts coverage, and we are the ones who get the call. | Equipment | Checkbox | List columnFilterMobileExport | 331 of 344 Dale Bishop |
Fields nobody fills in
A field library only ever grows, and nothing tells you what died. These are under 5% filled. Either they are asking for something people do not have, or nobody knows they exist. Retire them or move them somewhere people will see them.
- Manufacturer claim link warranty_claim_url9 of 3,104
- After-hours phone alt_phone_after_hours3 of 412
How these behave
- The machine key never changes once a field is published, because your exports, your filters and anything reading our API depend on it. The label can change any time.
- A field marked Customer sees prints on the documents for that record. Everything else stays inside your shop, including on the homeowner portal.
- Every field is in the CSV and JSON export by default, because an export missing your own fields is not an export.
- A field offered on mobile works with no signal, and syncs when the van reconnects.
- A field can be offered at one location only, which is how a second state gets a form the first one does not need.
- Deleting a field keeps the values on existing records for 90 days so a mistake is recoverable, then removes them.
- We do not cap how many you create, but the list shows you what nobody fills in.