> 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/writebackextreme/features/tableau-extension/end-user/add-data/overview.md).
# Overview
The example below shows how add-data can be used in a forecast scenario. The sheet at the top right shows the blended data of the original data and the data that is entered in writeBackExtreme. It uses the month and year combination as key for the blend relation. Clicking the mark enables the option to create a record for this specific datapoint.
After saving a record in the extension, the datasources are refreshed and the sheets will update their data based on the blend relationship.
## Saving table layout
On the overview page we allow saving the table layout which includes the `Rows per page` setting at the bottom and the sorting of the table. This is only available for the dashboard designer. Viewers will see this exact table state when they open the dashboard.
---
# 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.infotopics.com/writebackextreme/features/tableau-extension/end-user/add-data/overview.md?ask=&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.
