> 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/flow-components/kanban.md).

# Kanban

Every setting of the Avonni Kanban for screen flows: data mappings, column totals, card layout, actions, interactions, output variables and styling.

## Overview

The Avonni Kanban shows records as cards in columns, one column per value of a field such as Stage or Status. Users drag a card to another column and the Kanban saves the new value on the record. A sales manager can review the quarter's opportunities by stage and move a deal forward from the same screen.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FET6e0XjejXdASyrAFJCb%2Fkanban-kanban-overview.png?alt=media" alt="Opportunity Kanban in a screen flow, stages along a path, each column headed by a total and an average amount"><figcaption><p>Opportunities by stage, with a total and an average per column</p></figcaption></figure>

Each card is a record. The **Group Field Name** decides the columns, the **Card** mappings decide what a card shows, and **Group Summaries** put totals in the column headers. When a user drops a card in another column, the Kanban writes the column's value to the record, then runs the **Item Drop** interactions.

***

## Tutorials

Each tutorial builds on the same opportunity pipeline board. The [Kanban tutorials](https://docs.avonnicomponents.com/flow/tutorials/components/kanban.md) page groups them by what you want to do.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Build an opportunity pipeline board with column totals</strong></td><td>One column per stage, cards for each deal, and the total and average amount at the top of every column.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FVfHBopHsiJgyIuUhzeav%2Fflow-hub-cover-kanban.png?alt=media">flow-hub-cover-kanban.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/introduction.md">Build an opportunity pipeline board with column totals</a></td></tr><tr><td><strong>Move a deal and save it safely</strong></td><td>Drag a deal to another stage, let a validation rule refuse a bad move, and react to every saved one.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FhkoIJMsxNgdruHD0HNJZ%2Fkanban-cover-move-a-deal-and-save-it-safely.png?alt=media">kanban-cover-move-a-deal-and-save-it-safely.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/move-a-deal-and-save-it-safely.md">Move a deal and save it safely</a></td></tr><tr><td><strong>Open a flow from a card action</strong></td><td>Reassign or edit a deal from its card, in a side panel, and add a New Deal button above the board.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FRGK2bHbttTAtLJ14dgWW%2Fkanban-cover-open-a-flow-from-a-card-action.png?alt=media">kanban-cover-open-a-flow-from-a-card-action.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/open-a-flow-from-a-card-action.md">Open a flow from a card action</a></td></tr><tr><td><strong>Group cards into swimlanes with totals</strong></td><td>One lane per lead source inside every stage, with a total per lane.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FOxwil4TGcHgjuGByjFPc%2Fkanban-cover-group-cards-into-swimlanes-with-totals.png?alt=media">kanban-cover-group-cards-into-swimlanes-with-totals.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/group-cards-into-swimlanes-with-totals.md">Group cards into swimlanes with totals</a></td></tr><tr><td><strong>Filter, search and order a board</strong></td><td>Filters, a search bar and your own column order, so a long pipeline stays easy to read.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FKdxBdx75ilvSYJJ9HkiX%2Fkanban-cover-filter-search-and-order-a-board.png?alt=media">kanban-cover-filter-search-and-order-a-board.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/filter-search-and-order-a-board.md">Filter, search and order a board</a></td></tr></tbody></table>

***

## Projects

See this component in a complete Salesforce workflow. This project uses Avonni Dynamic Components and includes AI-assisted and manual build steps.

## Configuration

Click the Kanban on the flow screen to open its property editor. It has three tabs: **Properties**, **Interactions** and **Style**. The sections below follow the **Properties** tab.

### Data Source

| Data Source                                                                                       | Best for                                                                                                             |
| ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| [**Variable**](https://docs.avonnicomponents.com/flow/component-builder/data-sources/variable.md) | Records already in a flow collection variable, for example from a Get Records element.                               |
| [**Query**](https://docs.avonnicomponents.com/flow/component-builder/data-sources/query.md)       | Live records read by the Kanban itself, with filters, order and limit. Needed for the **Refresh Query** interaction. |

[Query or Variable](https://docs.avonnicomponents.com/flow/component-builder/data-sources/query-vs-variable.md) compares the two. [Build an opportunity pipeline board with column totals](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/introduction.md) sets up a Query board step by step.

### Data Mappings

#### Key Field

The unique identifier of each card. Required. Defaults to the record Id (shown as **Id** in the property editor). Every record needs a unique value here: the save after a drop and the output variables use it to find the record.

**Key Field**, **Group Field Name** and **Sub Group Field Name** are record references, written `{{Record.FieldApiName}}`. The field picker writes them that way; a bare API name typed in by hand is not read, so the board renders no columns or a dropped card is never saved. The card mappings under **Card**, and **Fields** in particular, take plain field API names instead.

#### Group Field Name

The field whose values become the columns, for example **Stage** on Opportunity or **Status** on Case. Required. **Group Field Record Type** limits the columns to the picklist values of one record type.

#### Group Summaries

One or more values in the header of every column. Each entry aggregates its own field and formats its own result, so a column can show a total and an average side by side.

| Setting                        | What it does                                                                                                                                                                                |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Field**                      | The record field to aggregate. Required.                                                                                                                                                    |
| **Aggregate Function**         | **Sum** (default), **Average**, **Count**, **Distinct Count**, **Min / Earliest**, or **Max / Latest**.                                                                                     |
| **Treat Blank Values As Zero** | Counts blank values as 0 instead of skipping them. Requires **Aggregate Function** = **Average** or **Count**.                                                                              |
| **Prefix** / **Suffix**        | Optional text shown before and after the value.                                                                                                                                             |
| **Display As**                 | **Number** (default), **Currency**, **Percent**, or **Date**. **Date** requires **Aggregate Function** = **Min / Earliest** or **Max / Latest**.                                            |
| **Type Attributes**            | Formatting for the chosen display type: currency code and display, minimum and maximum fraction, integer and significant digits, and the day, month, year, weekday and era parts of a date. |

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FIzZflxPhaGI595kBSHij%2Fkanban-summaries-panel.png?alt=media" alt="" width="320"><figcaption><p>Group Summaries and Sub Group Summaries, in the Data Mappings section of the property editor</p></figcaption></figure>

A board configured before 6.32.0 keeps working: its single summarize field is converted into one Group Summary with **Aggregate Function** set to **Sum**.

#### Sub Group Field Name and Sub Group Summaries

**Sub Group Field Name** splits every column into swimlanes, one per value of a second picklist field (for example one lane per **Lead Source**). Lanes come from picklist values only: a lookup such as **Owner** or a text field gives no lanes. **Sub Group Field Record Type** scopes it to one record type. **Sub Group Summaries** takes the same settings as **Group Summaries** and puts a total on every swimlane header. [Group cards into swimlanes with totals](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/group-cards-into-swimlanes-with-totals.md) builds one.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2F4kGbPsQQfdTE1FQmiQ58%2Fkanban-swimlane-totals.png?alt=media" alt=""><figcaption><p>A total on every column header, and a total on every swimlane header</p></figcaption></figure>

#### Card

| Mapping                       | What it shows                                                                                                  |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Cover Image**               | A field holding the URL of the card's cover image.                                                             |
| **Title**                     | The card title. **Linkify** renders it as a link.                                                              |
| **Description**               | The card body text. Rich text is supported.                                                                    |
| **Start Date** / **Due Date** | Date or date/time fields.                                                                                      |
| **Annotation Icons**          | One or more icons, each mappable to a field.                                                                   |
| **Infos**                     | Extra labelled items, each with an optional **URL** and **Target** (**Self**, **Blank**, **Parent**, **Top**). |
| **Avatar**                    | The card avatar: **Initials**, **Icon Name**, **Image Source** and **Presence Type**.                          |
| **Fields**                    | More record fields shown on the card.                                                                          |

#### Filters and Search Fields

**Filters** lists the fields users can filter the board on. **Search Fields** lists the fields the search bar looks through; the bar only appears when **Show Search** is on in the **Search** section. [Filter, search and order a board](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/filter-search-and-order-a-board.md) sets both up.

### Properties

| Setting                      | What it does                                                                                                                              |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Variant**                  | **Base**: each column has its own title. **Path**: the column titles form a chevron path across the top, like the path on a record page.  |
| **Show Item Count**          | Shows the number of cards beside each column title.                                                                                       |
| **Show Subgroup Item Count** | Shows the number of cards in each swimlane header.                                                                                        |
| **Hide Column Header**       | Hides the title row above the columns.                                                                                                    |
| **Highlight On Click**       | Highlights the last card the user clicked. An **Item Click** interaction of type **Open Flow Panel** highlights it even when this is off. |
| **Read Only**                | Turns off drag and drop.                                                                                                                  |

The Overview figure shows the **Path** variant, which suits stages that run in order, such as an opportunity pipeline. With **Base**, each column keeps its own title above its cards and nothing links the columns together. Pick it when the columns have no natural order, for example Cases grouped by type.

### Header

The area above the board.

| Setting                                | What it does                                                                                                                                                     |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title** / **Caption**                | The header text.                                                                                                                                                 |
| **Avatar**                             | An image, initials or a fallback icon, with **Size** and **Variant** (**Circle** or **Square**).                                                                 |
| **Is Joined**                          | Squares the bottom border and removes its shadow, so the header sits flush on the board.                                                                         |
| **Actions**                            | Header buttons (**Label**, **Name**, **Icon Name**, **Disabled**, **Hidden**, **Title**, **Alternative Text**). A click runs the **Header Action** interactions. |
| **Visible Actions Buttons**            | How many header actions show as buttons before the rest move to a menu.                                                                                          |
| **Hide Actions** / **Disable Actions** | Hide or disable the header actions menu.                                                                                                                         |

### Group By

| Setting                   | What it does                                                                                                             |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Hide Undefined Group**  | Hides the column of records with no value in the group field.                                                            |
| **Undefined Group Label** | The title of that column when it is shown.                                                                               |
| **Collapsed**             | Starts every swimlane closed, showing only its header. Columns are never collapsed. Empty swimlanes always start closed. |
| **Show Empty Sub Groups** | Shows swimlanes that hold no card.                                                                                       |

### Column Order Direction

**Direction** sets the column order: **Default** (the order of the field's values, for a picklist the order set in Setup), **Ascending Order**, **Descending Order**, or **Custom**. With **Custom**, **Columns Custom Order** lists the columns in your order, and a value left out of the list is hidden. See [Filter, search and order a board](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/filter-search-and-order-a-board.md).

### Card Actions

**Actions** adds items to the menu at the top right of every card. Each action has a **Label**, a **Name** (used by the **Target Name** of an interaction), and **Disabled** and **Hidden** settings. A click runs the **Item Action Click** interactions. [Open a flow from a card action](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/open-a-flow-from-a-card-action.md) wires one to a flow.

### Card Avatar

**Position** (**Left** or **Right**), **Variant**, **Size**, **Initials** (auto-formatted), **Fallback Icon**, **Presence Type** and **Presence Position**.

### Card Image

**Image Fallback**, **Position** (**Top** or **Bottom**), **Height**, **Crop Fit** (**Cover**, **Contain**, **Fill**, **None**), **Crop Position X** and **Crop Position Y**.

### Card Fields Layout

**Variant** sets how the **Fields** of a card show their label:

| Variant           | Display                                                    |
| ----------------- | ---------------------------------------------------------- |
| **Standard**      | The label above the value.                                 |
| **Label Hidden**  | The value only.                                            |
| **Label Inline**  | The label and the value side by side.                      |
| **Label Stacked** | The label directly above the value, with clear separation. |

### Filter

| Setting                         | What it does                                                                                                                           |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Display As Popover**          | Shows the filters in a popover instead of inline.                                                                                      |
| **Picklist Filter Sort Order**  | Orders picklist filter values **Ascending**, **Descending**, or by **Default Order of Field**.                                         |
| **Use Record Picklist Values**  | Fills filter options from the object's picklist values.                                                                                |
| **Use Cascading Filter Values** | Narrows the options of each filter to the records left by the other filters. When it is on, **Use Record Picklist Values** is ignored. |

Every filter menu has a **Filter mode** button that sets how its value is matched. Nothing to configure: the modes follow the field type, and users pick one as they filter.

* **List, text and picklist filters**: **Equals** (default), **Not Equals**, **Empty**, **Not Empty**.
* **Number, date and time range filters**: **Between** (default), **Not Between**, **Equals**, **Not Equals**, **Less Than**, **Less or Equal**, **Greater Than**, **Greater or Equal**, **Empty**, **Not Empty**.
* **Checkbox filters**: no mode button, always **Equals**.

**Empty** and **Not Empty** test the field itself, so the menu hides its value inputs when either is selected.

### Search

**Show Search** adds a search bar above the board. **Placeholder** sets its hint text and **Position** places it (**Left**, **Right**, **Center**, **Fill**). The fields it searches are set in **Search Fields**.

***

## Interactions

[Interactions](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel.md) set what happens when users act on the board. Add them in the **Interactions** tab.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FmpkuBw2ixcZTXmbS5eoW%2Fkanban-interactions-tab.png?alt=media" alt="Interactions tab of the Kanban property editor listing Item Action Click, Item Click, Header Action and Item Drop" width="320"><figcaption><p>The four Kanban interaction triggers in the Interactions tab</p></figcaption></figure>

| Interaction           | Runs when                                                        | Types added for the Kanban                                                                                                                         |
| --------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Item Click**        | A user clicks a card.                                            | **Open Flow Panel**; **Refresh Query** (Query only).                                                                                               |
| **Item Action Click** | A user clicks a card action. **Target Name** picks the action.   | **Open Flow Panel**; **Refresh Query** (Query only); **Delete Selected Record(s)**, **Duplicate Selected Record(s)**, **Edit Selected Record(s)**. |
| **Header Action**     | A user clicks a header action. **Target Name** picks the action. | **Open Flow Panel**; **Refresh Query** (Query only).                                                                                               |
| **Item Drop**         | The record of a dropped card has been saved.                     | **Open Flow Panel**; **Refresh Query** (Query only); **Update Record(s)**.                                                                         |

All four also offer the common types, such as **Show Toast**, **Navigate**, **Flow Navigation**, **Open Flow Dialog** and **Refresh All Queries**.

**Target Name** is a filter: the interaction runs only for the action whose **Name** it holds, and for every action when it is empty. The name of the clicked action is returned in **Clicked Item Action Name** or **Clicked Header Action Name**.

In an interaction that runs on a card (**Item Click**, **Item Action Click**, **Item Drop**), values can read the card's record, for example `{{Record.Id}}` to pass the record Id to a flow opened in a panel. The value picker lists the record's fields under **Record:**.

### How a drop is saved

1. The user drops a card in another column.
2. The Kanban saves the new group value on the record (and the new sub group value, with swimlanes). A **Success** toast confirms it.
3. If the save fails (a validation rule, a required field, a missing permission), an **Error Updating Record** toast shows the error and the card returns to its column. Since version 6.34, the **Item Drop** interactions do not run after a failed save.
4. After a successful save, the **Item Drop** interactions run.

**Item Drop** runs after the save, so it cannot stop a move. To refuse one, use a validation rule. In the property editor preview, a drop saves nothing and runs no interaction. **Update Record(s)** on **Item Drop** saves the dropped record again and runs its **On Success** or **On Error** interactions; with it, the **Edited Records** outputs stay empty. [Move a deal and save it safely](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/move-a-deal-and-save-it-safely.md) walks through the whole pattern.

***

## Output Variables

To use an output in a later flow element, pick the screen element, then the Kanban, then the output. Outputs are filled by the user's action on the screen.

### Item Click

| Output variable                   | Type   | What it returns                                                         |
| --------------------------------- | ------ | ----------------------------------------------------------------------- |
| **Clicked Item**                  | Record | The record of the clicked card.                                         |
| **Clicked Item Name**             | Text   | The **Key Field** value of the clicked card, usually the record Id.     |
| **Clicked Item Group Value Name** | Text   | The group value of the card's column, for example `Negotiation/Review`. |

### Item Action Click

| Output variable                          | Type   | What it returns                                              |
| ---------------------------------------- | ------ | ------------------------------------------------------------ |
| **Clicked Item Action Item**             | Record | The record of the card whose action was clicked.             |
| **Clicked Item Action Name**             | Text   | The **Name** of the clicked action, for example `reassign`.  |
| **Clicked Item Action Item Name**        | Text   | The **Key Field** value of that card, usually the record Id. |
| **Clicked Item Action Group Value Name** | Text   | The group value of that card's column.                       |

> **Example:** After the screen, a **Decision** element checks whether **Clicked Item Action Name** equals `reassign` and sends the flow to a reassignment screen that uses **Clicked Item Action Item**.

### Item Drop

| Output variable              | Type   | What it returns                                                                          |
| ---------------------------- | ------ | ---------------------------------------------------------------------------------------- |
| **Dropped Item**             | Record | The record of the dropped card.                                                          |
| **Dropped Item Key Field**   | Text   | The **Key Field** value of the dropped card, usually the record Id.                      |
| **Dropped Item Group Value** | Text   | The group value of the column the card was dropped in, for example `Negotiation/Review`. |

### Edited Records

| Output variable               | Type              | What it returns                                                         |
| ----------------------------- | ----------------- | ----------------------------------------------------------------------- |
| **Edited Records**            | Record Collection | Each record moved on this screen, with its new group value.             |
| **Edited Records Serialized** | Text              | **Edited Records** as JSON text.                                        |
| **Edited Records Full Data**  | Record Collection | Every record loaded on the board, the moved ones with their new values. |

The Kanban already saved each move. Use these outputs to read what changed, for example to log it or to show a summary on the next screen.

### Header Action

| Output variable                | Type | What it returns                            |
| ------------------------------ | ---- | ------------------------------------------ |
| **Clicked Header Action Name** | Text | The **Name** of the clicked header action. |

### Component Metadata

| Output variable     | Type   | What it returns                                    |
| ------------------- | ------ | -------------------------------------------------- |
| **Number of Items** | Number | The number of cards currently loaded on the board. |

### Flow Interaction Output Variables

Like other interactive Flow components, the Kanban has generic output slots (**Variable 1** to **Variable 10**) that an [Open Flow Dialog](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/open-flow-dialog.md) or [Open Flow Panel](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/open-flow-panel.md) interaction fills with values from the launched flow. See [Flow Interaction Output Variables](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/flow-interaction-output-variables.md).

***

## Styling

The **Style** tab groups its settings as follows.

| Group                                | Settings                                                                                                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Margin**, **Padding**              | Space around and inside the component.                                                                                                                       |
| **Size**                             | **Width**, **Height**, **Min Width**, **Max Width**, **Min Height**, **Max height**.                                                                         |
| **Border**                           | **Color**, **Size**, **Style**, **Radius** of the component border.                                                                                          |
| **Header**                           | **Background Color**, **Padding Top**, **Padding Right**, **Padding Bottom**, **Padding Left**, **Margin Bottom**.                                           |
| **Header Border**                    | **Color**, **Size**, **Style**, **Radius**, and the bottom border used with **Is Joined**.                                                                   |
| **Header Title**, **Header Caption** | **Color**, **Font Size**, **Font Style**, **Font Weight**.                                                                                                   |
| **Header Actions**                   | Text, background and border colors, each with an active and a hover color.                                                                                   |
| **Header Avatar**                    | **Background Color**, **Foreground Color**, **Border Radius**.                                                                                               |
| **Column Header**                    | **Path Background Color**: the color of the path. Applies to the **Path** variant only.                                                                      |
| **Column Header Summary**            | **Text Color**, **Font Size**, **Font Weight**, **Prefix/Suffix Text Color**, **Prefix/Suffix Font Size**, **Height**, **Line Height** of the column totals. |
| **Column Sizing**                    | **Min Width** and **Max Width** of a column.                                                                                                                 |
| **Card Color**                       | **Background**, **Background Focus**, **Background Hover**, **Background Highlight**, **Border**, **Border Focus**, **Border Highlight**.                    |
| **Card Title**                       | **Text Color**, **Link Color**, **Link Color Hover**, **Font Size**, **Font Style**, **Font Weight**, **Line Clamp**.                                        |
| **Card Description**                 | **Text Color**, **Font Size**, **Font Style**, **Font Weight**, **Line Clamp**.                                                                              |
| **Card Info**                        | **Text Color**, **Link Color**, **Link Color Hover**, **Font Size**, **Font Style**, **Font Weight**.                                                        |

Two more sets appear only when an interaction needs them:

* With an **Open Flow Dialog** interaction: **Flow Dialog Header** (background, bottom border, label color, size and weight) and **Flow Dialog Footer** (background, top border).
* With an **Open Flow Panel** interaction: **Flow Panel** (background color, border color, size, style and radius) and **Flow Panel Header** (background, bottom border, label color, size and weight, close icon colors).

***

## Troubleshooting

| Problem                                                                | Cause                                                                                             | Fix                                                                                    |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Cards cannot be dragged at all                                         | **Read Only** is on.                                                                              | Turn **Read Only** off in the **Properties** tab.                                      |
| A card will not start dragging                                         | The user pressed the card's action menu.                                                          | Press and hold the card body, away from the menu.                                      |
| A drop in the preview does not save                                    | The property editor preview never saves and runs no interaction.                                  | Test in a running flow.                                                                |
| The card goes back with an **Error Updating Record** toast             | The save was refused: a validation rule, a required field, or a group field the user cannot edit. | Read the toast message. Fix the data, the rule or the field-level security.            |
| The toast says "Errors concerning certain fields" with no rule message | The validation rule shows its error on a field.                                                   | Set the rule's **Error Location** to **Top of Page** so its message reaches the toast. |
| An **Item Drop** toast or flow did not run after a drop                | The save failed, so the interactions were skipped (since 6.34).                                   | Expected. Check the error toast.                                                       |
| No columns appear                                                      | **Group Field Name** is not set.                                                                  | Set it in **Data Mappings**.                                                           |
| The board is empty at runtime but shows cards in the preview           | With **Variable**, the collection is empty when the screen loads.                                 | Put the Get Records element before the screen and check it returns records.            |
| **Refresh Query** is missing from the interaction types                | The data source is **Variable**.                                                                  | Switch to **Query**, or refresh the collection in the flow.                            |
| Drop outputs are empty on the next screen                              | No card was dropped on this screen.                                                               | Add a **Decision** element that handles the empty case.                                |


---

# 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/flow-components/kanban.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.
