> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/keywords/lists/all.md).

# All

{% hint style="info" %}
The `ALL` keyword is used to access all entities in nested entities, bypassing the parent-rows.

For example, you have the entities `[Shop]` and `[Shop.Products]` where `[Shop.Products]` is the nested entity.\
When you use `Count([Shop.Products])`,  you’ll get number of products **from the current shop** only. \
If instead you want to **count all products from all shops**, you can write:

`Count(ALL [Shop.Products])`

This function is SQL compatible. For more information about SQL compatibility, see our [documentation](/platform/wemreference/sql-compatibility.md).
{% endhint %}

{% hint style="success" %}
Returns all entities of a given nested entity without limiting by active parent row.
{% endhint %}

<details>

<summary><code>all</code><mark style="color:blue;"><code>[entity]</code></mark></summary>

```
First( ALL [Shop.Products] 
    where [Shop.Products.ProductCode] = "X-00014-1297"
)
/* searches all products in all shops and returns the first product that has a specified product code */

List([Shop] 
    where RowId([Shop]) in 
        (
        RowId([Shop]) of ALL [Shop.Products] 
        where [Shop.Products.Price] >= 20 
            and [Shop.Products.Price] <= 30
        )
)
/* returns all shops that have a product in the price range between 20 and 30*/
```

</details>


---

# 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.wem.io/platform/wemreference/keywords/lists/all.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.