Skip to main content
add company-specific data to supported records without database schema changes. Define a field under Settings → Custom Fields. Alforse adds it to the entity’s form, stores it with built-in fields, and exposes it through the API.

​
Defining a field

The nine data types are Yes/No (boolean), Date, List, Numeric, Text, User, Customer, Supplier, and File. The three reference types store a reference to an existing Alforse record rather than free text. Forms render inputs for the first eight; File is defined but has no input on the entity form yet.

​
Which entities support custom fields

The catalog is curated, not universal — the settings page lists one row per eligible entity with its module and field count. Coverage spans most modules: Sales (customer, quote, sales order, sales invoice, RFQ, their contacts, locations and lines), Purchasing (supplier, purchase order, supplier quote, purchasing RFQ, their lines and contacts), Invoicing (purchase invoice, payment, memo), Items (part, tool, material, consumable, fixture, service, costing/planning records; see items), Resources (employee job, work center, department, location, process, shift), Inventory (receipt, shipment, warehouse transfer, picking list, shelf), Production (job), Quality (gauge, issue) and Accounting (account, payment term, journal). An entity not listed on the settings page isn’t supported yet.

​
How values save, and where they reach

Custom inputs appear below built-in fields and save to the entity’s customFields JSON column. The API exposes this column for reads and filters. Its keys are field IDs, not display names, so use the settings catalog to resolve definitions.