Website GitHub Try Demo

Custom Fields

Custom Fields let administrators add extra data fields to any record type in OpenMES without writing code. Define text, number, date, dropdown, or checkbox fields that appear on forms, in filters, and in reports.

Custom Fields management page with field list and filters

Field Types

Each custom field has a type that determines what data it stores and how it appears in the interface.

TypeDescriptionExample Use
TextSingle-line free text input.Customer PO number, external reference ID.
TextareaMulti-line text input for longer content.Special instructions, notes.
NumberNumeric value with optional decimal places.Target weight, tolerance percentage.
DateDate picker.Required delivery date, inspection due date.
DropdownSingle selection from a predefined list of options.Priority level, product category.
CheckboxBoolean true/false toggle.Requires certification, hazardous material flag.

Creating a Custom Field

To create a new custom field:

  1. Click + New Custom Field.
  2. Select the Entity this field belongs to (e.g., Work Order, Product, Batch, Machine).
  3. Set a unique Key – a machine-readable identifier used in the API and exports (e.g., customer_po).
  4. Enter a Label – the human-readable name shown on forms (e.g., "Customer PO Number").
  5. Choose the Type from the list above.
  6. Set whether the field is Required – required fields must be filled in before saving the record.
  7. Set the Position – controls where the field appears relative to other custom fields.
  8. Set the Status – active fields appear on forms; inactive fields are hidden but their data is preserved.

Filtering and Searching

The Custom Fields management page provides tools to find and organize your fields:

Customer-Specific Requirements: Use custom fields to capture data unique to your customers or industry. For example, add a "Customer PO Number" text field to work orders so operators can reference the customer's purchase order during production.
Regulatory Compliance: Custom fields are useful for tracking compliance-related data such as certification numbers, inspection dates, or environmental classifications. Because they appear in reports and exports, they integrate naturally into your audit trail.