> 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/v4.0/support/faq.md).

# FAQ

<details>

<summary>Does Apps for Tableau look at any of my data?</summary>

No, WriteBackExtreme is a on-premises solution without the need of any internet connection. Our SaaS solutions are hosted in an isolated Azure environment only accessible for a by you approved group of engineers.

</details>

<details>

<summary><strong>Is blending essential for the writeback functionality?</strong></summary>

You can use a blend, Join or Relationship to connect primary data with writeback data. With Data Correction you can write back in the primary data source (if on a live connection) and you only need a Blend/Join or Relationship if you want to combine your primary data with the writeback data in the same visualization. You can also use an ETL process to combine primary data with WriteBack data.

</details>

<details>

<summary>Can WriteBackExtreme run in docker  / kubernetes?</summary>

Yes WriteBackExtreme can run in a container. The configuration for this is next-level since it needs to be configured manually without the one-click installer.  Reach out to our support channel for the possibilities.

</details>

<details>

<summary>How to copy a schema to another database</summary>

WriteBackExtreme does not support transferring a schema to another database. The best option is to copy the table using the export/import function via management console and transfer the data itself using your own database management tool.&#x20;

1. Open the management console.
2. Go to schemas and select the schema you want to copy
3. Click the export button at the top right. A json fill will be downloaded in your browser
4. Click Schemas in the menu again
5. Click the import button
6. Select the connection to the other database
7. Click import. The table will be created.&#x20;
8. After this, export all data from your original table with your favorite database management tool and import it to the new table in the destination database table.&#x20;

Since we made a copy, all dashboards need to be reconfigured using the new schema.&#x20;

The easiest way to do this is trough the export/import functionality of the extension. This way  your dashboard extension settings are preserved.&#x20;

1. In the management console, open the schema.
   1. The url looks like this: https\://\[your-writebackextreme-url]/backend/schemas/84f7d654-f672-4e16-91fa-3b3d4c58c64b/
   2. The last part (excluding the / at the end) is the UUID of the new schema.&#x20;
   3. Copy this UUID.&#x20;
2. In your dashboard extension go to configuration
3. Select import/Export in the left menu
4. Click Download data file
5. Open the file in a text editor like notepad.
6. Search for the term `schema_key` in the file. The value should be a UUID (for example 9ab26ae5-5e5f-4142-ba6a-b61ac77f7a23)
7. Change the original UUID to the new one you copied from the management console.
8. Save the file
9. Go to the dashboard configuration again
10. Remove the old schema.
11. Import the data.json file you just edited on the import/Export page.
12. After importing you will see that the schema is added and all configuration is preserved.&#x20;

</details>


---

# 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/v4.0/support/faq.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.