# FAQ

Here is a list of frequently asked questions.

<details>

<summary>Does InputTables overwrite my existing data?</summary>

No, we do not touch your existing data. All the edits are safely stored in a separate table. When you (re)open SuperTables, it will connect to this table and join the data to your existing data.&#x20;

<img src="https://226224474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI9t4RSYLlrfjY1Kmrop5%2Fuploads%2FR5aQo2I2sQZLitR2ezC0%2FInputTables%20join%20data%20schematic.png?alt=media&#x26;token=c065b323-cf39-4873-9440-b2e0aee77d3c" alt="" data-size="original">

</details>

<details>

<summary>Can I re-use my edited data in other Tableau charts?</summary>

Yes! You are free to join the WriteBackExtreme table back to your primary datasource and use the values from WriteBackExtreme in your charts.&#x20;

</details>

<details>

<summary>Can I comment in pivot mode on a group of rows?</summary>

No. It is only possible to comment on a single cell.&#x20;

</details>

<details>

<summary>I click the comment or audit card in the side panel, but an incorrect cell highlights.</summary>

Likely, your primary key is not unique. Make sure that when you create a schema you do not see the warning "Your primary key is not unique".

</details>

<details>

<summary>Can I change my primary key for the schema?</summary>

No you cannot change your primary key. If you would change your primary key that will result in many orphan records. We recommend creating a new schema with the correct primary key.&#x20;

</details>

<details>

<summary>"Unable to reach WriteBackExtreme at this URL” when configuring InputTables in SuperTables</summary>

#### **Symptom**

When configuring **InputTables inside SuperTables**, the following error is shown after entering the WriteBackExtreme URL:

> **“Unable to reach WriteBackExtreme at this URL. Check that the server is online, configured for this address, and accessible from this environment.”**

This may occur even though:

* The WriteBackExtreme URL opens successfully in a browser
* The backend service is running and reachable on the network

As a result, the InputTables login screen does not appear and the integration cannot be completed.

***

#### **Cause**

This issue is caused by **browser-enforced Local Network Access restrictions** introduced in modern browsers (for example **Chrome 142+**).

When InputTables is used inside SuperTables:

* The extension runs in the browser context
* If the **extension is loaded from a public domain** (e.g. Tableau Cloud or a SaaS-hosted extension)
* And the **WriteBackExtreme backend resolves to a private/on-prem network address**

…the browser will **block the request before it reaches the server**, even if the URL is reachable directly in a browser tab.

This is a **security restriction enforced by the browser**, not a connectivity or configuration issue in InputTables or WriteBackExtreme.

***

#### **Resolution**

To resolve this issue, both the extension and backend must be hosted in the **same network context**:

✅ **Recommended**

* Use **on-prem hosting for both SuperTables/InputTables and WriteBackExtreme**

✅ **Alternative**

* Use a **fully public / SaaS setup** for both the extension and the backend

❌ **Not supported**

* Using a **public domain extension** with an **on-prem/private WriteBackExtreme backend**

There is **no supported workaround** within the browser, SuperTables, or InputTables for this scenario.

</details>