# Transaction List Filter

A single filter input for a transaction list. Each Transaction List Filter block is one filter (text, date, or select). Drop multiple instances side-by-side or in a sidebar to build a full filter panel above a Transaction List.

The block writes its value into the page's transaction filter state, which Transaction List reads and re-queries against.

## Available in

* Page modules
* Dashboard modules

## When to use

* Above any Transaction List block where users need to narrow results.
* Inside the **Transaction List** layout's *Filters* slot.
* For multi-criteria browsing (e.g. *Date range + Status + Customer*) — drop one filter block per criterion.

## Settings

| Setting       | Description                                                               |
| ------------- | ------------------------------------------------------------------------- |
| **Configure** | Opens the configuration modal — pick the field, operator, and field type. |

The configuration modal supports:

* **Field** — the transaction field this filter targets (e.g. *trandate*, *status*, *entity*).
* **Operator** — comparison: contains, equals, greater than, less than, between (depends on field type).
* **Field Type** — text, date, or select. Affects which input control is rendered.
* **Selected Options** — for select-type filters, the available values.
* **Padding** — spacing around the filter input. Default: 16.
* **Dynamic Value** (lightning bolt toggle) — when turned on, the filter's value is resolved at runtime from the current session instead of being set by the user. Use this to pre-filter the list automatically — for example, to always show only orders for the signed-in user's location. Enter a variable expression as the value (e.g. the current user's location or a session variable). Ask your Client Admin or In8Sync contact for the available variable names for your setup.

## How it works

1. On render, the block displays the configured input (text input, date picker, or dropdown).
2. As the user types or picks a value, the filter writes to the page's transaction-filter state.
3. Downstream Transaction List re-queries automatically with the new filter applied.
4. If no filter is configured yet, the block shows a placeholder reminder for the page builder.

The block reads the workflow's date format from session state for date fields, so a filter set up in MM/DD/YYYY input format renders correctly for users with a different display preference.

## Examples

**Date + status filter pair.** Two Transaction List Filter blocks in a Row above a Transaction List: one for *trandate* (date), one for *status* (select with the relevant statuses).

**Customer-search filter.** A single filter block on *entity* (text, contains operator) at the top of an Order History page. As the user types, the list narrows.

## 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 List</strong></td><td>The list block this filter drives.</td><td><a href="/pages/0HBWjwooyav8Uibdnaus">/pages/0HBWjwooyav8Uibdnaus</a></td></tr><tr><td><strong>Transaction List (layout)</strong></td><td>The layout block that has a Filters slot designed for these filter blocks.</td><td><a href="/pages/LMG5Zk0dNtZ4LInQmyDM">/pages/LMG5Zk0dNtZ4LInQmyDM</a></td></tr><tr><td><strong>Transaction Search</strong></td><td>An alternative search-driven approach for finding specific transactions.</td><td><a href="/pages/3LyKFu6XjQ0sX6BaDIUd">/pages/3LyKFu6XjQ0sX6BaDIUd</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-list-filter.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.