> 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.md).

# Setting up SuperTables with Data Service

This guide lets you get started with SuperTables with server side processing for large data sets.

SuperTables primarily relies on the Tableau Extensions API to retrieve summary data. As a result, most processing occurs on the client side, and all data is loaded at once. To address performance limitations with large datasets, we are introducing a new approach that leverages server-side processing. This significantly reduces client-side load and improves scalability. To use this feature, users must be on **SuperTables version 6.x.x or later** and **WriteBackExtreme version 6.x.x or later**.

{% hint style="info" %}
The Data Service is only available when you add SuperTables as a **dashboard extension**. In a viz extension, the option is shown as **External Data Service — Dashboard Extension only** and can't be selected. It's also not available in sandboxed extensions.
{% endhint %}

### Setting up a data source.

These steps require you to create a semantic model in the WriteBackExtreme environment. You can follow this guide here to create a semantic model in WriteBackExtreme [Semantic modeling](https://docs.infotopics.com/features/management-console/semantic-modeling.md)

On the **General** tab, under **Data fetching method**, select **External Data Service (WriteBack Extreme)**. The **Data Service Configuration** section appears below it. Click **Configure** to open the **Data Service Setup**.

<figure><img src="https://1304574535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe2zyseN6XFBaLs6YTcnd%2Fuploads%2Fgit-blob-06cd85fce95726a25b2b0923d4615214e96db0ff%2FSuperTables_DataService_GeneralTab.png?alt=media" alt="External Data Service selected on the General tab, with the Data Service Configuration section"><figcaption></figcaption></figure>

Once you're set up, this section shows the **WriteBackExtreme URL** and the **Semantic model** your SuperTable is connected to.

The **Data Service Setup** guides you through three steps: **Authentication**, **Data Source** and **Mappings**. A completed step gets a check mark, and you can click a step to go back to it.

{% stepper %}
{% step %}

### Authentication

Log in to your WriteBackExtreme environment. Please contact your WriteBackExtreme administrator for the login URL and credentials. When you're logged in, you'll see **Authentication Complete**; click **Continue to Data Source Selection**.

<figure><img src="https://1304574535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe2zyseN6XFBaLs6YTcnd%2Fuploads%2Fgit-blob-abc03cc9f695eaba1317f22b964c728542720816%2FSuperTables_DataService_Setup_Authentication.png?alt=media" alt="Authentication Complete in the Data Service Setup" width="420"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Data Source

Select the semantic model you created in WriteBackExtreme. When it's connected, you'll see **Data Source Connected**; click **Continue to Column Mappings**.

<figure><img src="https://1304574535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe2zyseN6XFBaLs6YTcnd%2Fuploads%2Fgit-blob-b5481b41820ca44cb3d52e651a6a68e24d8bb444%2FSuperTables_DataService_Setup_DataSource.png?alt=media" alt="Data Source Connected in the Data Service Setup" width="420"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Mappings

Map SuperTables columns to columns on your Tableau worksheets, so dashboard actions and filters work between Tableau and SuperTables. This step is explained in [Dashboard Actions and Mapping](https://docs.infotopics.com/supertables/configuration/setting-up-supertables-with-data-service/dashboard-actions-and-mapping.md). Click **Save & Close** when you're done.
{% endstep %}
{% endstepper %}

At the top of the setup you can use **Change Data Source** to connect to another semantic model, or **Logout** to log out of WriteBackExtreme.

#### Logging in as a user

Your users log in to the Data Service from the **Data Service** panel on the right side of the table. That's also where they can log out. When their WriteBackExtreme session expires, SuperTables logs them out and shows the login page in the panel again.

#### Choosing columns

Once a data source is connected, a list of all available columns is displayed. When the data source loads for the first time, all columns are disabled by default. Users can select only the columns they require, and this selection can be modified at any time from the Columns sidebar.

For very large datasets, loading all columns at once can negatively impact performance, so selecting only the necessary columns is recommended.

<figure><img src="https://1304574535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe2zyseN6XFBaLs6YTcnd%2Fuploads%2Fgit-blob-d0e6bc1ea3f81a3e34cbd7e2760a736f40349148%2FStep3.png?alt=media" alt="" width="335"><figcaption></figcaption></figure>

**Auto aggregation**

SuperTables with Data Service also support dynamic aggregation based on the visible columns in the table. This is a processing-intensive but very useful feature. When enabled, the data is aggregated based on the currently visible columns.

For example, if only **Category** and **Sales** are visible, the table displays unique categories with the sum of sales. If **Category**, **Region**, and **Sales** are visible, the table shows sales aggregated by category per region.

When this option is disabled, non-aggregated data is passed directly from the database to the grid.

#### Export limitations when using the External Data Service

When **External Data Service (WriteBackExtreme)** is selected as the data fetching method, **export options (CSV, XLS, PDF)** are intentionally disabled.

This behavior is **by design** for the following reasons:

**Performance**

* The External Data Service is typically used for **very large datasets**.
* Exporting large datasets directly from the extension could lead to **performance issues or very large file downloads**.

**Security**

* The data service provides **direct access to backend data sources**.
* Allowing unrestricted export could expose **large portions of the underlying dataset**, which may not be intended.

Because of this, export functionality is only available when using **Tableau Datasheet-based loading methods**, where Tableau controls the dataset size.

With the Data Service, the **Export** and **Tooltip** tabs are therefore not shown in the configuration screen, and the context menu has no export options. Use **Refresh data** in the context menu to load the latest data from the semantic model.


---

# 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/supertables/configuration/setting-up-supertables-with-data-service.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.
