# Transaction Record

A container that displays one transaction in full. Provides four slots — *Page Header*, *Header Fields*, *Line Items*, *Related Records* — that you fill with other blocks to build the layout you want.

By default the *Header Fields* slot starts with a 2-column Row layout so you can immediately drop **Record Field** blocks into it. The other slots are empty until you populate them.

![Transaction Record showing a 2-column header field grid at the top, line items table in the middle, and a related records section at the bottom](/files/prylJgqeVJm0KObc9hqx)

## Available in

* Page modules
* Order Form modules

## When to use

* Customer-service detail pages where the agent inspects a single transaction.
* "Edit existing order" flows on Order Form pages — Transaction Record loads the order and Order Lines edits it.
* Anywhere a single transaction's full detail (header + lines + related records) is the focus.

For multi-transaction list views, use **Transaction List** instead.

## Settings

| Setting                  | Description                                                                                                                  |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| **Configure**            | Opens the configuration modal — record type, custom form, visibility toggles.                                                |
| **Title**                | Heading text. Default: *Transaction Record*.                                                                                 |
| **Page Header slot**     | Optional — drop a Heading or any block to render above the record.                                                           |
| **Header Fields slot**   | Pre-populated with a 2-column Row + Columns. Drop Record Field blocks (the *Page* version, see Order Lines View doc) inside. |
| **Line Items slot**      | Drop **Order Lines** (the page-context version) here to render the line items.                                               |
| **Related Records slot** | Drop **Transaction Related Records** here to show linked records.                                                            |

The configuration modal supports:

* **Record Type** — which transaction type this block renders (`salesorder`, `cashsale`, etc.). Default: salesorder.
* **Form** — optional NetSuite custom form ID to use.
* **Show Header** — display the header fields slot. Default: Yes.
* **Show Lines** — display the line items slot. Default: Yes.
* **Show Related Records** — display the related records slot. Default: Yes.

## How it works

The block reads the current transaction from session state (typically loaded by **Transaction Search** in Load mode or by URL parameter) and renders the slots configured.

Each slot can hold any blocks — the slot system gives you full control over layout. For most transaction types, drop:

* A **Heading** in Page Header.
* Several **Record Field** (page version) blocks in a Row layout in Header Fields.
* An **Order Lines** (page version) block in Line Items.
* A **Transaction Related Records** block in Related Records.

{% hint style="info" %}
Transaction Record is a *container*. The actual data rendering happens in the blocks you put inside its slots. Empty slots render as empty space.
{% endhint %}

## Examples

**Customer-service order detail.** Transaction Records with a Page Header containing a Heading, Header Fields with Record Field blocks for date / customer / status, Line Items with Order Lines (page version), Related Records with Transaction Related Records showing fulfilments and invoices.

**Read-only invoice view.** Transaction Record with Record Type = invoice. Header Fields shows due date, balance, terms; Line Items shows the invoiced items.

## 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 Search</strong></td><td>The block that loads a transaction into Transaction Record.</td><td><a href="/pages/3LyKFu6XjQ0sX6BaDIUd">/pages/3LyKFu6XjQ0sX6BaDIUd</a></td></tr><tr><td><strong>Transaction Record — Order Lines View</strong></td><td>The page-context line items block that goes in the Line Items slot.</td><td><a href="/pages/kUZDOTeM0va1QEsAlznV">/pages/kUZDOTeM0va1QEsAlznV</a></td></tr><tr><td><strong>Transaction Record — View Field</strong></td><td>The page-context field block that goes in the Header Fields slot.</td><td><a href="/pages/iJwEY8a7NMkgQLDo2x1v">/pages/iJwEY8a7NMkgQLDo2x1v</a></td></tr><tr><td><strong>Transaction Related Records</strong></td><td>The block for the Related Records slot.</td><td><a href="/pages/AfpKE3tLebNIY3LLONcj">/pages/AfpKE3tLebNIY3LLONcj</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.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.