> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/determining-attributes/page-3.md).

# Filtering Determining Attributes

You can filter values against any other field in the same file.  In the files shown here, you can filter account currency by account type (since both are in the accounts data block).  You can filter the has\_app and has\_online attributes by customer type, as both are in the customers data block.  However, you cannot filter account type by customer type, since they are in two separate data blocks.

{% hint style="info" %}
You can create a consolidated data set when you are using TDX (see [TDX User Guide](/platform-docs/test-data-orchestrator-tdo/user-documentation/user-guide-for-tdx.md)) to extract data, as long as both schemas are in the same database.  E.g., if you had 'Customers' and 'Accounts' in the same database, you could extract both customer and account data and bring them into TDO as a single data block.  In this case it would be possible to group account type by customer type.
{% endhint %}

Filtering helps to prevent invalid data combinations from being selected by end users.

To create a filter, click on the pencil by the determining attribute name to open the ‘Edit Determining Attribute’ window.  (We are editing the ‘currency’ determining attribute.) Scroll down to the ‘Criteria’ section of the window (below the values section).  A list of all of the fields available for filtering will be shown.  We want to filter by  ‘account\_type’ so go to that line, and then select  ‘account\_type’ from the drop-down list on the right. 

<figure><img src="/files/d2FNHTo2NA5O5K1ZRYqJ" alt=""><figcaption><p>Setting a Determining Attribute filter</p></figcaption></figure>

Scroll up and click the ‘Save’ button to save the filter criteria. (In this use case, some account types are only offered in USD, but others are offered in all supported currencies.)

The impact of setting a filter is seen in the Business Rules section of TDO.  In this case, when you select an account type in your business rule, the currency values available for selection will be filtered to only display those that are available for your selected account type. &#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, and the optional `goal` query parameter:

```
GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/determining-attributes/page-3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.