> For the complete documentation index, see [llms.txt](https://docs.antsomi.com/cdp-365-user-guide-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antsomi.com/cdp-365-user-guide-en/insights/reports/filter-your-data/filter-examples.md).
# Filter examples
### Include only Jean, Lụa, or Cotton
Suppose you want to limit a chart's information to just data coming from the Jean, Lụa, or Cotton. Select the chart and add the following filter:
1. Include/Exclude: **Include**
2. Dimension: *Country*
3. Match Type: **Matches any**
4. Value: `Jean, Lụa, Cotton`
You could also do this using 3 OR clauses. But it's easier to use Matches any with a list.
### Exclude "(not set)"
To exclude "(not set)" values from your charts, use an Exclude filter. For example:
1. Include/Exclude: **Exclude**
2. Dimension: *Chất liệu*
3. Match Type: Is null
4. Value: `(not set)`
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.antsomi.com/cdp-365-user-guide-en/insights/reports/filter-your-data/filter-examples.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
