> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/supertables/configuration/setting-up-supertables-with-data-service/dashboard-actions-and-mapping.md).
# Dashboard Actions and Mapping
As mentioned in the previous section, with the introduction of the Data Service, SuperTables no longer rely on data from the Extensions API. Since the data now comes from two different sources within the same dashboard, we need to establish mapping relationships to correctly translate dashboard actions and filters between Tableau and the semantic model, using the column mapping feature.
#### Column mapping
Filter column mapping acts as a dictionary, translating column names while performing actions from Tableau to SuperTables and the other way around. A SuperTables column can be mapped to multiple sheet columns if needed.
First, select a SuperTables column from the first dropdown, then select a Tableau column that has been added to a sheet. You can also type in the field to make searching easier. The dropdown supports multiple selections.
Once added, the mappings will appear in the **All Mappings** section below. You can click the trash bin icon to remove a mapping. If all mappings associated with a SuperTables column are deleted, the entire row is removed automatically.
It is also possible to add a manual mapping entry. For example, if a sheet does not currently contain any data but the columns are already defined, the extension may not be able to fetch those columns. Similarly, if you expect a new column to be added later, you can create a manual mapping in advance.
To do this, click the **Manage** button in the **All Mappings** section, then enter the column name you want to map to the corresponding SuperTables column.
#### Dashboard actions
In the data service, you will need to select the **mapping** you made when setting up dashboard actions. This field determines which mapping is used when the action is triggered. Since a dashboard can contain multiple mappings, explicitly selecting the correct one ensures that the action corresponds to the intended data and behaves as expected.
---
# 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.infotopics.com/supertables/configuration/setting-up-supertables-with-data-service/dashboard-actions-and-mapping.md?ask=&goal=
```
`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.