# Customer Field

Renders one field from the currently selected customer in the Order Form context. The block auto-detects the field's type (text, select, date, boolean, number, email, etc.) and provides the right input control with required/disabled flags.

## Available in

* Order Form modules **only**

## When to use

* Order Form pages where you want to surface specific customer attributes in context (phone, email, credit limit, balance, custom fields).
* When you need to let the cashier or sales rep edit a customer field inline (notes, custom flags) during order entry.
* For richer multi-section customer detail, use **Entity 360 View** instead.

## Settings

| Setting       | Description                                                                           |
| ------------- | ------------------------------------------------------------------------------------- |
| **Configure** | Opens the configuration modal — field selection, label, width, type-specific options. |

The configuration modal supports:

* **Field Name** — which customer field. Options come from the customer record's available fields (5-min cache).
* **Field Label** — display label. Defaults to the field name.
* **Width** — input width in pixels. Default: 200.
* **Field Type** — auto-populated from the field's actual type (text, boolean, select, date, longtext, readonly, email, number).
* **Field Options** — for select fields, the available options (auto-populated).
* **Required** — make the field required to submit. Default: No.
* **Disabled** — render read-only. Default: No.
* **Default Value** — pre-fill value if the customer field is empty.

## How it works

1. Reads the selected customer from session state (set by Customer/Vendor Selection).
2. Auto-resolves the field's type and options from the NetSuite customer field definition (cached for 5 minutes).
3. Renders the appropriate input control (text input, select, checkbox, date picker, etc.).
4. Date fields convert between MM/DD/YYYY (display) and YYYY-MM-DD (HTML5 input).
5. Edits write back to the customer record via the order submission flow.

{% hint style="info" %}
**Field Type and Field Options** auto-populate when you pick a Field Name — you don't need to set them manually. They re-resolve when the field changes.
{% endhint %}

## Examples

**Display customer phone on order form.** Customer Field with Field Name = `phone`, Field Label = *Phone*, Disabled = Yes (read-only).

**Editable customer notes.** Customer Field with Field Name = `comments`, Field Label = *Notes*, Required = No. Cashier can update notes during the order.

**Credit limit visibility.** Customer Field with Field Name = `creditlimit`, Field Label = *Credit Limit*, Disabled = Yes. Helps the cashier see the customer's credit at a glance.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Record Field</strong></td><td>The general-purpose field block for transaction-level fields.</td><td><a href="/pages/CvoZuH76L8oKeiLSjA0a">/pages/CvoZuH76L8oKeiLSjA0a</a></td></tr><tr><td><strong>Customer/Vendor Selection</strong></td><td>Selects the customer this block reads from.</td><td><a href="/pages/km19hjFIFOFjRK0yQAJp">/pages/km19hjFIFOFjRK0yQAJp</a></td></tr><tr><td><strong>Entity 360 View</strong></td><td>For richer multi-section customer detail.</td><td><a href="/pages/iZxOk2Qc3Jd4I8EhpErq">/pages/iZxOk2Qc3Jd4I8EhpErq</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/transaction-components/customer-field.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.