> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/kanban-board/features/fetchxml-criteria.md).

# FetchXML Criteria

This property allows you to set your Kanban board to create groups dynamically using the FetchXML query.\
\
You can specify a FetchXML query in the FetchXML Criteria field within the entity configuration record, as shown in the screenshot below:

<figure><img src="/files/miZn7vs01urPTv6CLN5B" alt="FetchXML Criteria"><figcaption></figcaption></figure>

This feature will work when you select the lookup field in the Row Grouping. For example, if parent account field is selected then the fetch xml should be of the same entity as the lookup field i.e. account. Cards will then be displayed according to this row grouping.

**Before Fetch XML Criteria:**

<figure><img src="/files/ckRqVB9gEklH4H2tNZQC" alt="FetchXML Criteria"><figcaption></figcaption></figure>

**After using Fetch XML Criteria:**

Only rows that meet the specified FetchXML query will be created, and cards will be grouped in that rows accordingly. Other rows and records that don’t match the query will not be shown on the board.

<figure><img src="/files/HZ5aVXivm4Xq5TlyIvfm" alt="FetchXML Criteria"><figcaption></figcaption></figure>

&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inogic.com/kanban-board/features/fetchxml-criteria.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.