> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/tutorials/advanced-tutorials/embed-a-story-with-user-attributes/dynamic-tables.md).

# Dynamic Tables

To further customize your data retrieval based on user attributes, especially when working with dynamic tables in your SQL queries, you can dynamically adjust your query. This approach is ideal for personalizing and refining your dataset extraction from potentially different tables based on user settings or preferences.

**How to Implement:**

1. Switch the SQL editor to SQL code mode.
2. Identify the FROM clause in your query.
3. Integrate the user attribute condition by substituting the placeholder with your desired attribute.

Consider the example below for incorporating a table attribute directly into your query:

```sql
SELECT * 
FROM "breezy"."{{ (user or {}).get('attributes', {}).get('table', 'deals_breezy') }}"
```

The example demonstrates how to dynamically select appropriate table. This method leverages conditional logic to either use the `table` attribute or default to `deals_breezy` if the attribute doesn't exist.

{% @arcade/embed url="<https://app.arcade.software/share/raBTIcTNqt5jSBfUuiDt>" flowId="raBTIcTNqt5jSBfUuiDt" %}


---

# 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-v3.toucantoco.com/tutorials/advanced-tutorials/embed-a-story-with-user-attributes/dynamic-tables.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.