Carbon

Custom fields

Company-defined extra fields that attach to core records like customers, parts, and orders.

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

Defining a field

One row per eligible entity; the field form locks its data type after creation.
FieldType
The label shown on the record's form. Unique per table, per company.
One of ten types (below). Once saved, the type can't be changed; delete and re-create to switch.
Required only for the List type: the dropdown's choices.
The field must be filled before the form saves. Boolean fields are never treated as required.
Scopes the field to records carrying a matching tag; leave empty to show it on every record of the table.

The ten data types are Boolean, Date, List, Numeric, Text, Link, File, User, Customer, and Supplier. The three reference types store a reference to an existing Carbon record rather than free text.

A Link field holds a web address, such as a supplier's product page. Tables and record panels show it as a link that opens in a new tab, without the https:// and www. (hover to see the full address). An address typed without https:// gets it added when the link opens. Only http and https addresses become links; any other value shows as plain text.

NOTE

The data type is permanent

Carbon locks the data type after creation. To change it, create a replacement field and migrate existing values.

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, sales order, sales invoice, RFQ, their contacts and lines), Purchasing (supplier, purchase invoice, supplier quote, RFQ lines), Items (part, tool, material, consumable, costing/planning records; see items), Resources (employee job, work center, equipment, department, location), Inventory (shipment, warehouse transfer, picking list), Production (job), 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.

HEADS UP

CSV import and export skip custom fields

The CSV flows map built-in fields only; neither import nor the table download touches the customFields column. Populate custom fields on the form or through the API; see import and export for what CSV does cover.