Lookup & Autofill

Lookup fields

A lookup stores the selected record ID while showing useful business text. Choose the related table, value field and verified display fields rather than asking users to type an internal ID.

• Related table: the approved source module or core table.
• Value field: normally the source primary key.
• Display fields: concise identifiers users can recognise.
• Filters: structured conditions that limit eligible source records.

Run field actions on change

One source field can run multiple ordered actions. This is useful when selecting a Project must load project details and then reload the Job choices for that project.

1. 01
   Select the trigger field

   Choose the lookup whose value change starts the action sequence.

2. 02
   Add source-field loading

   Map verified source fields into the corresponding current-form fields.

3. 03
   Add dependent lookup reload

   Filter the dependent lookup by the current parent selection and clear stale values.

4. 04
   Review action order

   Actions run in the configured order, so place authoritative loading before dependent behaviour that uses it.

Authoritative server loading

Autofill is not only a convenience. Important source values—such as account IDs or customer details—should be reloaded from the selected source record on create and update so browser-posted values are not trusted.

• Use source-field loading for read-only snapshots and authoritative ledger IDs.
• Use model snapshot components when a historical JSON snapshot is required.
• Keep dependent dropdown filters structured and company-scoped.
• Test edit mode to confirm lookup selections and dependent choices are restored.

Related-record history

A record-history action can show prior records at the bottom of a create/edit form—for example, earlier bills for the selected Project and Job.

• Choose the source module and match one or more source fields to current-form fields.
• Select only the useful display columns.
• Choose an appropriate date, number or currency format and alignment.
• Treat the result as read-only context; it does not replace authoritative server validation.