> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/profile-and-settings/organization-settings/configurable-fields.md).

# Configurable Fields

Define custom fields (text, select, multiselect, boolean, date) with visibility rules, and attach them to requests, orders, suppliers, parts, and users

The **Configurable Fields** section allows you to create and manage custom fields that can be added to different resources across Silkline (e.g., Requests, Orders, Suppliers, Parts, Users). This gives you flexibility to capture organization-specific data and standardize information collection.

## Field Definitions

Custom field definitions are created centrally and can then be configured for use on specific resources. Each field definition includes:

* **Display Name** — The label shown to users
* **Description** — Optional help text explaining the field's purpose (shown in tooltips)
* **Field Type** — Text, Select, Multiselect, Boolean, or Date
* **Visibility** — Controls who can see the field:
  * **Internal only** — Only visible to users in your organization
  * **Signed-in suppliers** — Visible to suppliers who sign in with a magic link
  * **Anyone with a share link** — Visible to anyone who opens a share link, as well as signed-in suppliers
* **Read-Only** — When enabled, the field value can only be set by integrations or system processes
* **Options** — For Select and Multiselect fields, define the available choices
* **Segment Delimiter** — For Labeled Select fields whose option names are made of parts, the character that separates the parts (for example `|`). Choose a character that never appears inside a part. When set, users pick an option one part at a time instead of scrolling one long list, both on records and when choosing the field's default value.

## Creating Custom Fields

1. Navigate to **Organization Settings** → **Configurable Fields**
2. Click **Create Custom Field**
3. Fill in the field details (name, type, visibility, etc.)
4. For Select/Multiselect fields, add the available options
5. Save the field definition

Once created, the field can be added to specific resources from their respective settings pages.

## Viewing Field Definitions

The **Configurable Fields** table lists every field definition:

* Columns show each field's **Display Name**, **Type**, **Options**, **Default Value**, **Properties**, and **Linked To** resources, plus one column per integration. **Visibility** and **Read-Only** columns can be turned on from **Columns**
* Search matches a field's display name, description, internal name, or integration ID
* Filters narrow the list by **Type**, **Linked To** resource, and each integration's sync status
* Click a row to open the field's detail page

### Bulk editing fields

With [data cleaning mode](https://docs.silkline.ai/administration-tools/data-cleaning-mode.md) on, the table shows a checkbox on every row. Select fields, click **Edit**, and set **Visibility** or **Read-Only** on all of them at once. Fields are deleted one at a time from their detail page.

## Core Fields vs Custom Fields

* **Core Fields** — Standard fields built into Silkline (e.g., Payment Terms, Delivery Terms). These can be overridden with custom configurations on a per-resource basis.
* **Custom Fields** — Organization-specific fields that you create to capture unique data requirements.

## Configuring Fields for Resources

After creating a field definition, you configure it for use on specific resources:

1. Go to the resource settings page (e.g., **Orders**, **Requests**, **Suppliers**, **Users and Access**)
2. In the **Configurable Fields** section, click **Add Custom Field** or **Add Core Field Override**
3. Select the field definition you want to add
4. For a custom field, enter an **Internal Name**, the identifier the field's values are stored under on that resource. A core field override uses the core field's built-in name.
5. Configure whether the field is **Required** for that resource
6. Save the configuration

Each resource can have its own set of configured fields, and the same field definition can be used across multiple resources with different required settings.

An internal name can belong to only one field on a given resource, including the built-in names of core field overrides. Silkline rejects a name that another field on the same resource already uses, ignoring case, so `costCenter` and `CostCenter` count as the same name. Different resources can reuse the same internal name.

A **Required** field must hold a value both when the record is created and whenever the field is edited afterward. Clearing a required field is not saved — the field shows an error until a value is entered.

### Values that fill in from other records

When the same field definition is configured on more than one resource, a new record picks up the value already held by a related record. Each field takes the first value found, in this order:

1. **The record it is created from.** An order created from a request or quote, a quote created from a request, and a duplicated record keep the source's value.
2. **The supplier.** On orders, a field also configured on **Suppliers** takes the selected supplier's value.
3. **The requester.** A field also configured on **Users** takes the value set on the record's requester.
4. **The buyer.** Used when the requester has no value for the field.
5. **The field's default value.**

A quote has no requester or buyer of its own, so it uses the requester and buyer of the request it is created from.

Changing the supplier, requester, or buyer on a new order or request re-applies this order to each affected field and replaces what the field held, unless the value came from the record it was created from. Editing a saved record never changes its values.

New line items follow the same idea. A line takes the header's value for a shared field first, then the requester's, then the buyer's, then the field's default. A part's value fills only the line fields that are still empty after that. Lines copied from a request or quote keep the values they were copied with.

### Filtering by custom fields

Each custom field on a table appears as a filter under **Custom Fields**. Every field type except checkboxes offers a **Not set** option that finds records where the field is empty. A record counts as empty when the field was never filled in or was cleared, and an empty multi-select counts too.

* **Select and multi-select fields:** pick **Not set** alone or together with options, so **Not set** plus **Steel** lists records that are empty or set to Steel. Switch the operator to **is not** with **Not set** selected to list only records that have a value.
* **Text and date fields:** check **Not set** below the search box or date picker. It replaces any text or date range entered in the filter.
* **Checkbox fields:** **False** includes records where the box was never checked.

### Ordering custom fields

The **Custom Fields** table lists a resource's custom fields in the order they appear across Silkline: in create and edit forms, as table columns, on record details, and on generated PDFs. To change the order, drag a row by its handle to a new position. The new order is saved as soon as you drop the row. A newly added field goes to the end of the list.

Reordering requires permission to edit configurable fields. Users without it see the table in the saved order, with search and no drag handles.

{% hint style="warning" %}
**Important note:** To provide flexibility required for stable integrations, Configurable Field options act as data validation:

* Changing or removing an option does not automatically modify or remove existing data
* When editing an existing value that is no longer valid, the validation is enforced and the user must update the value to a valid option
  {% endhint %}

## Syncing Fields from Integrations

A custom field or supported core field override can be linked to a field in a connected external system — for example a NetSuite custom field or list, a Ramp accounting field, a First Resonance ION attribute, or a Microsoft Dynamics 365 Business Central dimension. Linking is done from the field's integration sidebar on its detail page.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-aea569e7435e6fc788832f5a57e4c2c575605263%2Fconfigurable-fields-integration-sidebar.png?alt=media" alt="Configurable field detail page with the integration sidebar open"><figcaption><p>Integration sidebar for a linked configurable field</p></figcaption></figure>

{% hint style="warning" %}
Integrations and field mappings may look up a custom field on each resource by its **internal name**. Renaming the internal name may stop the field's values from syncing until every mapping uses the new name, so Silkline asks you to confirm before it saves a new internal name. To rename one, use the field's **Edit** action in the **Configurable Fields** section of the resource's settings page (e.g., **Orders**), or in **Resource Associations** on the field's detail page.
{% endhint %}

### Fields used by field mappings

An integration's field mappings can read a custom field into Silkline (**Pull**), write it to the external system (**Push**), or both (**Bidirectional**). Only enabled mappings count.

* In the **Configurable Fields** table, a mapped field shows a mapping icon in its **Properties** column. Hover over it to see each mapping's integration, record type, external field, and direction.
* The field's detail page has a **Field Mappings** section that lists the same mappings.
* A mapped field can't be deleted, and it can't be removed from a resource that a mapping uses it on. The disabled button names the integration. Disable or remove the mapping first.

### Core field writeback

When a core field override is linked for writeback, its current core value is the source of truth for the linked external field. It takes precedence over a stored Configurable Field value or integration default targeting the same field. Clearing a clearable core field sends an explicit clear, so an older external value or configured default is not restored. Required values still enforce their normal validation; for example, a Coupa requisition line without an awarded Quantity fails writeback instead of clearing Quantity.

The available core fields and their native-field behavior depend on the integration. For Coupa requisition writeback, supported Request fields are **Need Date**, **Instructions**, and **Rationale**; supported Request Line fields are **Need Date** and **Quantity**. Linked Need Date and Rationale values move to the configured custom field and suppress their corresponding native values as documented, while Quantity is mirrored to the custom field and retained in Coupa's required native quantity field. See [Linked purchase-request core fields](https://docs.silkline.ai/configuration/integrations/coupa#linked-purchase-request-core-fields) for the header and line rules.

### Automatic refresh

Linked fields are refreshed from the external system automatically on a daily cadence. Each refresh re-pulls the field and **all of its options**, so new or renamed options appear in Silkline and expired options are removed without any manual action.

### Manual pull

You can also pull a linked field on demand from the field's integration sidebar. This fetches the latest version of the field and its options immediately.

### Pausing automatic updates (sync lock)

To stop a linked field from receiving updates, enable the **lock** toggle on the field's integration sidebar. While locked:

* Incoming changes from the external system are blocked, and the daily automatic refresh skips the field
* Silkline's version of the field and its options is preserved as-is

{% hint style="warning" %}
Pulling a locked field manually will unlock it and overwrite Silkline's version with the external system's data.
{% endhint %}
