> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/filter-search-and-order-a-board.md).

# Filter, search and order a board

Add filters, a search bar and your own column order to an opportunity board, so each rep narrows a busy pipeline to the deals they need.

Forty deals on one board is a lot to scan. A rep preparing a call wants only new business from partners, or the one deal she is about to discuss, and has no use for the **Closed Lost** column. This page adds filters and a search bar above the board, and sets which stage columns appear and in what order.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Ffi1TmN1y2LLBATa4NH3W%2Fkanban-filter-search-and-order-a-board-result.png?alt=media" alt="Opportunity Kanban with a search bar and three filter menus above it, filtered to new business: 11 deals, column totals recalculated"><figcaption><p>Filtered to new business: the counts and totals follow the filter</p></figcaption></figure>

## Before you start

* Build the pipeline board first: [Build an opportunity pipeline board with column totals](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/introduction.md). This page adds to that board.

## Steps

{% stepper %}
{% step %}

### Choose the filter fields

Open the Kanban in the property editor. In **Data Mappings**, add fields to **Filters**: **Type**, **Lead Source** and **Close Date**. Drag them in the list to set their order on screen.

Each field becomes a filter menu above the board. Picklist fields offer their values, a date field offers a range. The filter mode a user can pick (**Equals**, **Between** and so on) follows the field type: see [Kanban](https://docs.avonnicomponents.com/flow/flow-components/kanban.md) for the full list.

The column totals follow the filters: filter on **Type** = **New Business** and each `Total` shows the new business amount only.
{% endstep %}

{% step %}

### Make the filters work together

Open the **Filter** section:

* **Use Cascading Filter Values**: turn it on. Once a user picks a **Type**, the **Lead Source** menu only lists sources that have deals of that type. The menus list values, and their counts, from every opportunity in the org, not only the deals on the board, so a pick can still leave a column empty.
* **Picklist Filter Sort Order**: **Ascending** (the default) sorts picklist values alphabetically. **Default Order of Field** keeps the order set in Setup.
* **Display As Popover**: off, the filters sit in a row above the board. On, they move into one filter button that opens a popover, which saves room on a smaller screen.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fvr6Qwt59cZMgfSfwn9k7%2Fkanban-filter-search-and-order-a-board-filter-group.png?alt=media" alt="Filter section of the Kanban property editor with Use Cascading Filter Values turned on" width="320"><figcaption><p>Cascading filters narrow each menu to what the other filters leave</p></figcaption></figure>
{% endstep %}

{% step %}

### Add a search bar

In the **Search** section, turn on **Show Search**. Set **Placeholder** to something that tells users what they can type, for example `Search deals by name`, and pick a **Position** above the board.

Then, in **Data Mappings**, add **Opportunity Name** to **Search Fields**. Without **Search Fields**, the search looks in every searchable field of Opportunity, which matches more than users expect.
{% endstep %}

{% step %}

### Set your own column order and hide a stage

Open **Column Order Direction** and set **Direction** to **Custom**. **Columns Custom Order** fills with every stage.

* To reorder, drag the rows of the **Columns Custom Order** list. Users cannot move columns at runtime: the order you set here is the one they get.
* To hide a stage, remove it from **Columns Custom Order**. Remove **Closed Lost** and lost deals no longer appear on the board.

A board grouped by an optional picklist (for example **Lead Source** instead of **Stage**) also gets a column for records with no value. Hide it with **Hide Undefined Group** in the **Group By** section, or rename it with **Undefined Group Label**. Grouping by **Stage** never adds one, because Stage is required.
{% endstep %}

{% step %}

### Save and test

Save and run the flow. You should see:

* a filter menu for each field, labelled with the field label (**Opportunity Type**, **Lead Source**, **Close Date**), and a search bar, above the board;
* no **Closed Lost** column;
* after picking **New Business** in **Opportunity Type** (the filter applies at once and a line under the search bar says how many items were found): only new business cards, column totals for those cards, and a **Lead Source** menu limited to matching sources.
  {% endstep %}
  {% endstepper %}

## Troubleshooting

<details>

<summary>A stage added in Setup does not show on the board</summary>

**Direction** is **Custom**, and the new value is not in **Columns Custom Order**. With a custom order, the board shows only the stages in that list. Add the value to the list.

</details>

<details>

<summary>The search bar is missing</summary>

**Search Fields** alone does not show it. Turn on **Show Search** in the **Search** section.

</details>

<details>

<summary>The search finds deals for the wrong reason</summary>

**Search Fields** is empty, so the search looks in every searchable field of Opportunity. Add only the fields users actually search on.

</details>

<details>

<summary>A filter lists values that return no card</summary>

**Use Cascading Filter Values** is off. Turn it on to narrow each menu to the records that match the other filters.

</details>

## Related tutorials

* [Build an opportunity pipeline board with column totals](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/introduction.md): the board this page starts from.
* [Group cards into swimlanes with totals](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/group-cards-into-swimlanes-with-totals.md): split the same board by lead source.
* [Open a flow from a card action](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/open-a-flow-from-a-card-action.md): act on a deal straight from its card.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/tutorials/components/kanban/filter-search-and-order-a-board.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
