Custom fields

Custom fields let an administrator extend MaxTrax with extra data points beyond the built-in ones — for example a classification, a reference code, or a project-specific attribute. You define each field once, and its values are then recorded against individual records and shown where those records are displayed.

Before you start

• Configuring custom fields is admin-only. You need a Corporate Administrator role or higher; MaxTrax shows “You need a Corporate Administrator role or higher to manage custom fields” otherwise.
• Definitions are a single shared catalog — they apply across your projects, not per project.

What a custom field is

Each field definition has:

• Code — a stable identifier for the field (for example, project.classification).
• Type — the kind of field (see Field types).
• Label — the human-readable name people see.
• Description — optional helper text.
• Position — controls the order fields are shown in.
• Required — whether a value is expected.

Code and type are permanent

Code and Type are permanent once a field is created. You can change the label, description, position, and required flag afterwards, but not the code or type — this keeps stored values from ever mismatching the field they belong to. If you need a different code or type, create a new field.

Which entities support custom fields

Custom-field values can be recorded against four kinds of record:

• ISO (isometric drawing)
• Weld
• Inspection
• Welder

Field types

The available types are Text, Number, Date, Select, MultiSelect, Checkboxes, RadioButtons, Table, FileUpload, and Password for data entry, plus the structural/display types Heading, Subheading, Label, Fieldset, Fieldsets, Resolve, and None. You pick the type when you create the field, and it can’t be changed later.

Configure a custom field

The Custom fields admin screen lists your definitions with their Code, Type, Label, Pos (position), Req (required), Status, and per-row actions.

The list is shown a page at a time (25 rows by default — change it with the rows-per-page control beside the pager), so on a project with hundreds of definitions the quickest way to find one is the Search fields box rather than paging through. Search looks at every definition on the project, not just the page you’re on, and the column headings sort the whole list the same way. Export downloads everything currently matching your search, not only the visible page.

1. Select New field. Enter a Code, choose a Type, and give it a Label (and an optional Description). Set whether it’s Required and its Position, then select Create.
2. To change a field, select Edit on its row and update the label, description, position, or required flag.
3. To retire a field, use the deactivate (trash) action. The field becomes Inactive but its history is kept. Toggle Show inactive to see retired fields, and use the restore action to reactivate one.

Note

Some fields are generated (marked with a Gen badge). For these, only the label and description are editable — “Generated field — only label and description are editable” — and they can’t be deactivated.

Where custom fields appear

On the ISO detail Info tab, the Custom fields section lists the values recorded against that ISO as a read-only label-and-value list. Two markers keep the record honest as your configuration changes:

• (removed field) — the value’s field definition has since been deleted.
• (inactive) — the value belongs to a field that has been deactivated.

When an ISO has no recorded values, the section shows No custom fields defined.

Because values are stored on the record itself, they travel with that record’s data and are available to exports and reports built from it.

Note

In this release, entering and editing custom-field values doesn’t yet have a dedicated in-app screen — the catalog you manage here is the source of the labels and types, and the ISO Info tab is where recorded values currently surface.

Related

• Admin overview
• ISO detail — where ISO custom-field values are shown.