# Transaction Record — View Field

A read-only field display designed for the **Header Fields** slot of a Transaction Record. Pick a transaction field — it auto-resolves the field type and renders with the right format (text, currency, date, number, boolean, badge).

> **Note on naming:** This block's palette label is **Record Field** — same as the editable [Record Field](/client-admin-guide/active-workflows/getting-started/transaction-components/record-field.md) used in Order Form modules. They're different blocks: the editable Record Field is for entering values during order entry, this one is for displaying values from an already-loaded transaction.

## Available in

* Page modules **only**

## When to use

* Inside the **Header Fields** slot of a Transaction Record block.
* Building a custom transaction-detail layout where you control which fields appear and where.
* Anywhere a single transaction field needs to be displayed (not edited).

For editable transaction fields on Order Form pages, use the editable [Record Field](/client-admin-guide/active-workflows/getting-started/transaction-components/record-field.md).

## Settings

| Setting       | Description                                                                   |
| ------------- | ----------------------------------------------------------------------------- |
| **Configure** | Opens the configuration modal — field selection, label, format, display type. |
| **Title**     | Block title shown above the value. Default: *Transaction View Field*.         |

The configuration modal supports:

* **Field Name** — which transaction field. The field type and options auto-populate when you pick a field.
* **Field Label** — display label.
* **Field ID** — internal identifier (auto-resolved).
* **Field Type** — auto-detected: text, currency, date, number, boolean, badge.
* **Field Options** — for select fields (auto-populated).
* **Display Format** — text (default), currency, date, number, boolean, badge.
* **Display Type** — form-group (label above value) or inline (label and value on the same line). Default: form-group.
* **Decimal Places** — for numeric/currency formats: *auto* (use NetSuite's setting) or a fixed number. Default: auto.
* **Show Preview** — show dummy data in edit mode so you can see what the layout looks like. Default: Yes.

## How it works

1. Reads the current transaction's header fields from session state.
2. Resolves the configured Field Name and applies the configured Display Format.
3. **In edit mode** — shows generated dummy data (when *Show Preview* is on) so the layout is visible without a real transaction loaded.
4. **At runtime** — shows the actual value, or a skeleton loader while data loads.
5. If the field is missing from the loaded transaction, the block doesn't render.

{% hint style="info" %}
The block works only when a transaction is loaded into session state. Place inside a **Transaction Record** that's been populated by a **Transaction Search**.
{% endhint %}

## Examples

**Order header date.** Transaction Record — View Field with Field Name = `trandate`, Display Format = date, Display Type = form-group. Dropped into a Header Fields Column.

**Status badge.** Field Name = `status`, Display Format = badge. Renders the status as a coloured pill — handy at the top of an order detail.

**Customer name (inline).** Field Name = `entity`, Display Format = text, Display Type = inline. Renders compactly alongside other fields.

## 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>Transaction Record</strong></td><td>The container this block lives inside.</td><td><a href="/pages/of84ubYT3satrYOeSfPK">/pages/of84ubYT3satrYOeSfPK</a></td></tr><tr><td><strong>Record Field (editable)</strong></td><td>The Order Form version for actually entering field values.</td><td><a href="/pages/CvoZuH76L8oKeiLSjA0a">/pages/CvoZuH76L8oKeiLSjA0a</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/transaction-record-view-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.