> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/dynamic-data-filters.md).

# Add dynamic data filters

Use dynamic filters in a flow to filter data

## Action name: "Create a dynamic filter"

Dynamic filters let the user who generates the document choose which filter to apply to a child object of the document template.

Generation with dynamic filters can only be done through a Salesforce flow.

**In a Salesforce flow:**

### Add the Create a dynamic filter action

* **Condition on query**: Enter the condition used to retrieve the records. What is expected is what comes after the **Where** of a SOQL query
* **Document template object Id**: Enter the ID of the document template child object affected by the filter.\
  You can retrieve this value with a Get Records element in the flow.

### Create a collection variable

Create a collection variable in your flow. This variable will store the result of the dynamic filter.

### Assign values to the collection variable

Add an Assignment element to assign the result of the dynamic filter to the collection variable.\
To do this, use the Add operator with the output of the Create a dynamic filter action.

### Fill in the collection variable in the generation action

In the document generation action, enable the "Collection of Dynamic Filters" parameter, then enter the collection variable used previously.

{% hint style="warning" %}
**Tip**

Two example flows are available in the pre-built Flow Org
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/dynamic-data-filters.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.