Field Settings
Every module in ServCraft has custom fields that businesses can configure to match their own terminology and processes. Field Settings controls whether each field is visible, required, labelled correctly, and shown at creation.
What Are Field Settings?
ServCraft allows each business to customise the fields shown on records. This means:
- A field that's blank by default can be renamed and made mandatory
- A field that's shown by default can be hidden if the business doesn't use it
- A field can be hidden on the creation form but visible on the detail page
This is managed per module from the relevant settings page.
Where to Find Field Settings
Each module has its own field settings:
| Module | Settings path |
|---|---|
| Customers | Settings → Customers → Settings tab |
| Jobs | Settings → Jobs → Settings tab (works differently — see below) |
| Inventory | Settings → Inventory |
| Assets | Settings → Assets |
| Queries | Settings → Queries → Settings tab |
Jobs are the exception. On the Jobs Settings tab, custom fields are renamed (their labels changed), but there are no per-field Active/Required/Hide-on-create toggles like the other modules. Making a job field required is done per job status instead — see "Making Job Custom Fields Required" below.
What Can Be Configured Per Field
| Property | What it does |
|---|---|
| Is Active | Shows or hides the field in the UI. If OFF, the field is completely hidden — even if it has data. |
| Display Name | The label users see. e.g., rename "Custom Field 1" to "Contract Number". |
| Is Required | Makes the field mandatory before a record can be saved. |
| Hide on Create | Hides the field on the creation form, but shows it on the edit/detail page. Useful for fields that are filled in after creation, not at intake. |
| Description | Help text shown below the field (tooltip or subtitle). Guides users on what to enter. |
Custom Field Types Available
Different field types serve different purposes:
Hide on Create
Use this for:
- Fields that are filled in later in the workflow (e.g., "Date of first contact" only known after the initial conversation)
- Fields that require looking something up after creation
- Fields that are only relevant for certain record types (but you still want them visible post-creation)
Important: A field hidden on create cannot be required on create. If it's required AND hidden on create, the user will be blocked from creating any record of that type.
Standard Fields vs. Custom Fields
Field Settings mainly covers custom fields (text, number, date, checkbox), but on some modules a handful of standard fields are managed through the same interface. On Customers, for example, Customer Type, Industry Type, Media Type, Customer Status, Account Manager, VAT Number, and Company Reg Number can all be activated and made required from the Settings tab (though the drop-down ones can't be renamed).
Core identity fields like Customer Name, Email Address, and Job Status are not configurable through this interface. Job fault codes are made required per status in Settings → Jobs → Statuses.
Making Job Custom Fields Required
Important: Job custom fields cannot be made required through the Jobs Settings tab. To make a job custom field required, it must be added as a status option on the specific job status in Settings → Jobs → Statuses → [target status] → status options, and that option set to Required rather than Optional. It is then enforced when someone moves a job into that status.
All ten job custom fields are available as status options: the four text fields, the two Yes/No checkboxes, the two dates, and the two numbers. Each one can be added as Optional (shown at the status change but not enforced) or Required (the status change is blocked until it is filled in). The same list also carries non-custom options such as fault codes, supplier and purchase order details, and materials.
Record Sequence (Numbering) by Module
Modules that generate numbered records have a configurable sequence, found on that module's settings page:
| Module | Where configured |
|---|---|
| Job Card | Settings → Jobs → Settings tab |
| Recurring Job | Settings → Jobs → Settings tab |
| Quote | Settings → Quotes |
| Invoice | Settings → Invoices |
| Purchase Order | Settings → Purchases |
| Project | Settings → Projects |
Each supports a Prefix (text before the number) and a Sequence Value (next number to use), with a preview of the latest record number. Multi-store businesses can configure the prefix per store.
If the accounting integration is set to use the accounting system's invoice numbering sequence, invoice numbers from Settings → Invoices are temporary. Each invoice takes the accounting system's number when it syncs. See Accounting Integration.
Option Lists (Types, Statuses, Reasons)
Beyond field settings, most modules also have configurable drop-down option lists:
| Module | Options available |
|---|---|
| Customers | Types, Statuses, Industry Types, Media Types (how they heard about you), Designations — each is a tab in Settings → Customers |
| Jobs | Statuses, Job Types, Fault Codes, Fault Causes, Fault Reasons — each is a tab in Settings → Jobs |
| Queries | Types, Statuses, Reasons — each is a tab in Settings → Queries |
These are separate from field settings but just as important. If a dropdown list doesn't have the right options, users either leave the field blank (data quality problem) or pick the wrong option.
Import and Field Mapping
For inventory imports, Required settings on fields are only enforced for Category and Subcategory. If either is set to Required in Settings → Inventory, every import row must have a value in that column or the row fails with "Category Required" or "Subcategory Required". See Inventory Items for the full list of required inventory import columns.
Worked Example: Configuring a "Contract Number" Field
Business needs: Every customer must have a contract number. This should appear on all customer records and on job cards.
Steps:
- Settings → Customers → Settings tab
- Add "Custom Text Field 1" to the active fields
- Set its Name (display name) = "Contract Number"
- Set Required = true (if it's truly mandatory for every customer)
- Leave Hide On Create off (so staff must enter it when creating the customer)
Changes save as you make them.
If you also need a contract number on job records, rename a job custom field on Settings → Jobs → Settings tab, and make it required per status via Settings → Jobs → Statuses if needed.