AWRA Help Center

Custom fields are configured at Settings → Custom Fields. You pick a module, define fields, and they appear on that module's create, edit and detail screens for everyone in your organization. They are your data, scoped to your workspace, and they travel with the record.

Field Types

Text, long text, whole number, number, money, percentage, date, date and time, yes/no, single select, multi select, and file. Choosing the right type matters more than it looks: a money field formats and totals correctly, a date field can be filtered and reported on as a date, and a select keeps everyone using the same words instead of eleven spellings of the same supplier.

Where They Can Go

Custom fields are supported across the operational record set — around forty-five modules — including:

• Inventory: items, adjustments, warehouses, locations, stock transfers, inventory counts.
• Assets: assets and asset custodians.
• Procurement: vendors, supplier applications, vendor portal users, RFQs, quotations, requests, purchase orders.
• Sales & POS: customers, contacts, addresses, tax settings, invoices and invoice lines, payments, credit notes, POS sales, counters, cash sessions.
• Finance: accounts, expenses.
• People & delivery: employees, departments, users, roles, projects, project tasks, support tickets.
• Automation: workflows, workflow tasks, approval runs and steps, exceptions, runs and logs.

Filling Them In Bulk

A field added after records already exist starts empty. Rather than opening a hundred records, use the module's bulk values screen to set the new field across many records at once — the usual move right after adding a field to a live module.

Before You Add One

• Check nothing already covers it. Categories, statuses, reasons, projects and tags already exist and are reportable; a custom field duplicating one of them splits your data in two.
• Prefer a select over free text for anything you will later group or filter by.
• Name it for the person filling it in, not for the system.
• Deleting a field removes the data captured in it. If a field is obsolete, consider removing it from the form before removing it altogether — deleted definitions, options and values are recoverable from Trash, but do not rely on that as a plan.

Permissions

Configuring fields is a settings permission; filling them in is part of editing the record itself. So the people using a field do not need any extra access to use it — see the Permissions Guide.