> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/infobridge-wb-matrix-only/9.-data-transformations/filter-rows.md). # Filter rows Add filters to retain only rows required in the target visuals. You can specify filter conditions, only the rows that satisfy the conditions will be available in the query. Let's consider the sample report below to demonstrate how to filter data.

We can use the filter configuration shown below to retain only the rows with "Domestic" or "North America" as the global market and COGS > 200k.

You need to specify the options listed below to configure a filter: * **Column name:** The measure or dimension on which the filter is based. * **Operator**: This can change depending on the data in a column. For text data, use conditions are is/is not/in/not in. For numeric data, use conditions like is/is not/less than/greater than/less than or equal to/greater than or equal to etc. * **Value:** Either key in the string/number or select from the dropdown. * **Add Filter:** Click the link to add multiple and/or conditions. Notice how the rows have been filtered out from the report based on the filter conditions specified.

--- # 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.inforiver.com/infobridge-wb-matrix-only/9.-data-transformations/filter-rows.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 `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.