> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/connectors/connector-repositories/reporting-tool/tableau.md).

# Tableau

This article outlines the integration with Tableau, enabling streamlined metadata management through features such as crawling, delta crawling, report previews, and lineage building (both automatic and manual).

The connector establishes connectivity with Tableau through REST APIs. For Tableau On-Premises, access requires a service account username and password. For Tableau Online, token-based authentication requires a token name, token, and Content URL.

<div align="left"><figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2FOw3SrLebfUWS0ZgYY4O3%2Fimage.png?alt=media&amp;token=5ec3f904-7805-4908-b5dc-2451c1a5f9f5" alt=""><figcaption></figcaption></figure></div>

## Overview

### Connector Details

| Connector Category                                                          | Reporting Tools      |
| --------------------------------------------------------------------------- | -------------------- |
| OvalEdge Release Supported                                                  | Release3.0 and later |
| <p>Connectivity</p><p>\[How the connection is established with Tableau]</p> | REST APIs            |
| Verified Tableau Versions                                                   | 8.3 to 2025.1        |

{% hint style="info" %}
*The Tableau connector has been validated with the mentioned "Verified Tableau Versions" and is expected to be compatible with other supported Tableau versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.*
{% endhint %}

### Connector Features

| Feature                                                                                                                          |                                                                 Availability                                                                 |
| -------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------: |
| Crawling                                                                                                                         |                                                                       ✅                                                                      |
| Delta Crawling                                                                                                                   |                                                                       ✅                                                                      |
| Profiling                                                                                                                        |                                                                      NA                                                                      |
| Query Sheet                                                                                                                      |                                                                      NA                                                                      |
| Report Preview                                                                                                                   |                                                                       ✅                                                                      |
| Auto Lineage                                                                                                                     | <p>✅<br>To learn more, click <a href="/release7.2/connectors/connector-repositories/reporting-tool/tableau/tableau-lineage.md">here</a>.</p> |
| Manual Lineage                                                                                                                   |                                                                       ✅                                                                      |
| Secure Authentication via Credential Manager                                                                                     |                                                                       ✅                                                                      |
| Data Quality                                                                                                                     |                                                                      NA                                                                      |
| DAM (Data Access Management)                                                                                                     |                                                                       ✅                                                                      |
| Bridge                                                                                                                           |                                                                       ✅                                                                      |
| [Chrome Extension Supported](https://docs.ovaledge.com/home/browser-extension/features-and-operations#view-certification-status) |                                                                       ✅                                                                      |

### Metadata Mapping

The following objects are crawled from Tableau and mapped to the corresponding UI assets.

<table data-search="false"><thead><tr><th width="170">Tableau Object</th><th width="163">Tableau Property</th><th width="173">OvalEdge Attribute</th><th width="185">OvalEdge Category</th><th width="188">OvalEdge Type</th></tr></thead><tbody><tr><td>Projects</td><td>Top Level Project</td><td>Report Group</td><td>Report Group</td><td>Report Group</td></tr><tr><td>Projects</td><td>Sub Projects</td><td>Report Group</td><td>Domain</td><td>Domain</td></tr><tr><td>Projects</td><td>Project Descriptions</td><td>Source Description</td><td>Descriptions</td><td>Description</td></tr><tr><td>Workbook</td><td>Workbook Name</td><td>Report Name</td><td>Reports</td><td>Workbook</td></tr><tr><td>Workbook</td><td>Workbook description</td><td>Source Description</td><td>Description</td><td>Description</td></tr><tr><td>Workbook</td><td>Workbook type</td><td>Type</td><td>Reports</td><td>Workbook</td></tr><tr><td>Datasource</td><td>Datasource Name</td><td>Report Name</td><td>Reports</td><td>Datasource</td></tr><tr><td>Datasource</td><td>Datasource description</td><td>Source Description</td><td>Description</td><td>Description</td></tr><tr><td>Datasource</td><td>Datasource type</td><td>Type</td><td>Reports</td><td>Datasource</td></tr><tr><td>Views</td><td>View Name</td><td>Report Name</td><td>Reports</td><td>View / Visual Name</td></tr><tr><td>Views</td><td>View Type</td><td>Type</td><td>Reports</td><td>View</td></tr><tr><td>Visuals</td><td>Visual Filed</td><td>Report Column</td><td>Report Columns</td><td>Dimensions, Measures, Calculated Fields</td></tr></tbody></table>

## Set up a Connection&#x20;

### Prerequisites

The following are the prerequisites to establish a connection:

#### **Service Account User Permissions**

{% hint style="warning" %}
*It is recommended to use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.*
{% endhint %}

{% hint style="info" %}
**👨‍💻Who can provide these permissions?** These permissions are typically granted by the Tableau administrator, as users may not have the required access to assign them independently.
{% endhint %}

| Objects              | Access Permission                           |
| -------------------- | ------------------------------------------- |
| Connector Validation | Site Administrator or Explore (Can Publish) |
| Crawling             | Site Administrator or Explore (Can Publish) |
| Lineage              | Site Administrator or Explore (Can Publish) |
| Delta Crawling       | Site Administrator                          |
| Workbooks            | Site Administrator or Explore (Can Publish) |
| Views                | Site Administrator or Explore (Can Publish) |
| Sites                | Site Administrator or Explore (Can Publish) |
| Data Sources         | Site Administrator or Explore (Can Publish) |
| Sourcecode           | Site Administrator or Explore (Can Publish) |

{% hint style="info" %}
*Delta crawling requires revision history permissions to be enabled. These permissions are enabled automatically for site administrators. For the 'Explore (Can Publish)' role, they must be enabled manually.*
{% endhint %}

### Connection Configuration Steps

{% hint style="warning" %}
*Users are required to have the Connector Creator role in order to configure a new connection.*
{% endhint %}

1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for **Tableau**, and complete the required parameters.

{% hint style="info" %}
*Fields marked with an asterisk (\*) are mandatory for establishing a connection.*
{% endhint %}

<table><thead><tr><th width="219.83331298828125">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>Tableau</strong>" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the dropdown list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add Ons</td><td><ul><li>Select the checkbox for Auto Lineage Add-On to build data lineage automatically.</li><li>Select the checkbox for Data Access Add-On to enable the data access functionality.</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Tableau connection</p><p>(Example: "Tableaudb").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (e.g., PROD, STG) configured for the connector.<br>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</td></tr><tr><td>Connector Description</td><td>Enter a brief summary or details about the connector.</td></tr><tr><td>Host Name*</td><td>Enter the Hostname or IP address of the Tableau server.</td></tr><tr><td>Is Token Based Auth (Yes/No) *</td><td><p>Tableau consists of two types of authentication:</p><ol><li><strong>Tableau On-Premises</strong>: If the user selects ‘<strong>No</strong>’ from the dropdown, they must enter the Service Account username and password.</li><li><strong>Tableau Online</strong>: If the user selects ‘<strong>Yes</strong>’ from the dropdown, they must provide token details.</li></ol></td></tr></tbody></table>

{% tabs %}
{% tab title="Token-based authentication - Yes" %}

<table data-search="false"><thead><tr><th width="220.25">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Token Name*</td><td>Enter the Tableau's Token Name. The token name refers to the name assigned to the authentication token or key.</td></tr><tr><td>Token*</td><td><p>Enter the Token related to the specific Token name. It </p><p>could be an API key, an OAuth token, a session ID, or </p><p>any other string used to authenticate the application with the data source.</p></td></tr><tr><td>Tableau API Version*</td><td><p>Tableau versions supported are from 2.0 up to 3.24.</p><p><em><strong>Note</strong>: The Tableau REST API version must be compatible with the Tableau Server version. For REST API version compatibility details, click</em> <a href="https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_versions.htm#rest-api-versioning"><em>here</em></a><em>.</em></p></td></tr><tr><td>Connection String*</td><td><p>Configure the connection string:</p><ul><li><p>Automatic Mode: The system generates a connection string based on the provided credentials.</p><ul><li>Example (Tableau): https://{server}/api/3.9</li></ul></li><li><p>Manual Mode: Manually enter a valid connection string by enabling the toggle.</p><ul><li>Example (Tableau): https://{customized server}/api/3.9</li></ul></li></ul><p><em><strong>Note</strong>: Replace placeholders with actual database details.</em></p></td></tr><tr><td>Content URL</td><td><p>Enter the name of the Tableau On-Premise site. </p><p>For more details, click <a href="https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_auth.htm">here</a>.</p><p><em><strong>Note</strong>: Content URL is mandatory when Token-Based Authentication is set to <strong>Yes</strong>.</em></p></td></tr><tr><td>Crawl All Sites</td><td>Select <strong>Yes</strong> to crawl all sites, or <strong>No</strong> to restrict crawling to specified sites.</td></tr><tr><td>Alias Host Name</td><td>Enter the alias hostname used for connecting to the Tableau server.</td></tr></tbody></table>
{% endtab %}

{% tab title="Token-based authentication - No" %}

<table data-header-hidden data-search="false"><thead><tr><th width="220.25">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>User Name*</td><td>A username is required to connect to the Tableau server. To access the Tableau environment, enter the service account name.</td></tr><tr><td>Password*</td><td>Enter the password of the Tableau server.</td></tr><tr><td>Tableau API Version*</td><td><p>Tableau versions from 2.0 to 3.24 are supported.</p><p><em>The Tableau REST API version must be compatible with the Tableau Server version. For REST API version compatibility details, click</em> <a href="https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_versions.htm#rest-api-versioning"><em>here</em></a><em>.</em></p></td></tr><tr><td>Connection String*</td><td><p>Configure the connection string:</p><ul><li><p>Automatic Mode: The system generates a connection string based on the provided credentials.</p><ul><li>Example (Tableau): https://{server}/api/2.6</li></ul></li><li><p>Manual Mode: Manually enter a valid connection string by enabling the toggle.</p><ul><li>Example (Tableau): https://{customized server}/api/2.6</li></ul></li></ul><p><em><strong>Note</strong>: Replace placeholders with actual database details.</em></p></td></tr><tr><td>Content URL</td><td><p>Enter the name of the Tableau On-Premise site. </p><p>For more details, click <a href="https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_auth.htm">here</a>.</p><p><em><strong>Note</strong>: This is mandatory when validating with Tableau Online.</em></p></td></tr><tr><td>Crawl All Sites</td><td>Select <strong>Yes</strong> to crawl all sites, or <strong>No</strong> to restrict crawling to specified sites.</td></tr><tr><td>Alias Host Name</td><td>Enter the alias hostname used for connecting to the Tableau server.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

{% hint style="info" %}
If the connector encounters "Access Denied" errors during crawling, verify the following configuration values:

* Tableau REST API version is set to 3.9 or later.
* Content URL is configured correctly.
* Crawl All Sites is set to Yes when crawling multiple sites.
  {% endhint %}

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="219.8333740234375"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the dropdown list. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220.58331298828125"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security and Governance Admin. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="219.6666259765625"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p><strong>Example</strong>: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="220.6666259765625"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
*To perform crawl operation, users must be assigned the Integration Admin role.*
{% endhint %}

The **Crawl/Profile** button allows users to select one or more reports/report columns for crawling.

1. Navigate to the Connectors page and click **Crawl/Profile.**
2. Select the reports/report columns to crawl.
3. The **Crawl** option is selected by default.
4. Click **Run** to collect metadata from the connected source and load it into the **Data Catalog**.
5. After a successful crawl, the information appears in the **Data Catalog > Report / Report Column** tab.

The **Schedule** checkbox allows automated crawling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the **Select Period** drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the **crawl** operation at the scheduled time.

### Other Operations

The Connectors page provides a centralized view of all configured connectors, along with their health status.

#### **Managing connectors includes:**

* **Connector Health**: Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details.

#### **Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the **Nine Dots** menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the connection's integrity.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Configure Server Dialects for source code parsing and Connector Priority for table lineage connection. For more details, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings#lineage-applicable-for-reports-and-etls-etl-connectors-reports).
  * **Others**: Configure notification recipients for metadata changes.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

## Limitations

<table><thead><tr><th width="96.727294921875">Sl. No</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Tableau Hyper Reports are currently not supported in OvalEdge.</td></tr></tbody></table>

## Troubleshooting <a href="#connectivity-troubleshooting" id="connectivity-troubleshooting"></a>

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned **support team**.

{% tabs %}
{% tab title="Connectivity" %}

<table><thead><tr><th width="63.24609375">Sl. No</th><th width="220.45703125">Error Message</th><th width="437.04296875">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Error while validating connection: SSL handshake failed, unable to find valid certification path to requested target</td><td><p>The secured on-premises Tableau Server uses a TLS certificate that is not imported into the application.</p><p><strong>Resolution</strong>:</p><ul><li>Obtain the TLS certificate configured on the on-premises Tableau Server.</li><li>Import the certificate into the application using the dedicated certificate troubleshooting steps.</li><li>Validate the connection again after importing the certificate.</li></ul></td></tr><tr><td>2</td><td>Error while validating connection: site not found, invalid content URL specified</td><td><p>The Content URL is missing or does not exactly match the Tableau site when using a personal access token.</p><p><strong>Resolution</strong>:</p><ul><li>Enter a valid site name in the Content URL field exactly as it appears in Tableau.</li><li>Leave the Content URL blank only when the account has server administrator access.</li><li>Re-enter the correct site name and validate the connection again.</li></ul></td></tr><tr><td>3</td><td>Error while validating connection: user does not have access to the requested site</td><td><p>The connection account does not have sufficient access to the requested Tableau site or sites.</p><p><strong>Resolution</strong>:</p><ul><li>For access to multiple sites, request the Server Administrator role.</li><li>For specific sites, assign Explorer Can Publish or Site Admin Explorer individually.</li><li>Confirm the role change is saved in Tableau and validate the connection again.</li></ul></td></tr><tr><td>4</td><td>Error while validating connection: unsupported API version requested</td><td><p>The selected API version is not supported by the connected Tableau Server or Cloud environment.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the Tableau Server or Cloud version currently in use.</li><li>Select the API version mapped to the Tableau version in the reference documentation.</li><li>If the exact version is unknown, start with the commonly supported 3.9–3.11 range and adjust based on validation results.</li></ul></td></tr><tr><td>5</td><td>Error while validating connection: connection refused, unable to establish requested channel</td><td><p>The connection string does not match the security configuration of the Tableau environment.</p><p><strong>Resolution</strong>:</p><ul><li>Use https://&#x3C;host>/api/&#x3C;version> for Tableau Cloud and SSL-enabled on-premises Tableau Server.</li><li>Use http://&#x3C;host>/api/&#x3C;version> only when the on-premises Tableau Server does not use SSL.</li><li>For Tableau Cloud, always use https://.</li><li>For an on-premises Tableau Server that uses HTTPS with a private or self-signed certificate, import the certificate into the OvalEdge/Bridge Java truststore.</li></ul></td></tr><tr><td>6</td><td>Error while validating connection: Error Code: 401001 Signing Error Error signing in to Tableau server.</td><td><p>This error occurs when the authentication request to the Tableau Server fails due to invalid or incorrect login credentials.</p><p><strong>Resolution:</strong></p><ul><li>Verify that the Tableau Server username and password are entered correctly.</li><li>Re-enter the credentials and retry the connection validation.</li><li>Ensure that the account has the required permissions to access Tableau Server.</li><li>For details related to other error codes, refer to the <a href="https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_errors.htm#:~:text=These%20can%20include%20400%20(Bad,example%2C%20making%20a%20GET%20request">Tableau - Handling Errors in the REST API</a>.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## FAQs

{% tabs %}
{% tab title="Authentication" %}

<table><thead><tr><th width="58.4296875">S. No</th><th width="199.58984375">Question</th><th width="464.76171875">Answer</th></tr></thead><tbody><tr><td>1</td><td>What is the difference between a personal access token and a username and password when connecting to Tableau?</td><td><p>Two authentication methods are available:</p><ul><li>Personal Access Token: Preferred for both Tableau Server and Tableau Cloud.</li><li>Username and Password: Available only for Tableau Server.</li><li>Tableau Cloud requires a personal access token.</li><li>Username and password can be used for Tableau Server when the user doesn’t want to generate a Personal Access Token.</li></ul></td></tr><tr><td>2</td><td>Why does the Content URL field sometimes need a site name and sometimes not?</td><td><p>The Content URL field is used to enter the Tableau site name.</p><ul><li>Personal access token: A site name is required.</li><li>Username and Password: The Content URL can be left empty unless the account has Server Administrator access to all sites.</li></ul></td></tr><tr><td>3</td><td>What level of access is needed on the Tableau side to allow crawling to work correctly?</td><td><p>The required access depends on the number of sites being crawled:</p><ul><li>Site Admin Explorer: Suitable for specific individual sites.</li><li>Explorer Can Publish: Can also be used for relevant sites.</li><li>Server Administrator: Recommended when crawling many or all sites.</li><li>Server Administrator access removes the need to configure roles separately for each site.</li></ul></td></tr><tr><td>4</td><td>Is a certificate always required to connect to an on-premise Tableau server?</td><td><p>No. A certificate is required only when the on-premise Tableau server is secured and a TLS-related connection issue occurs.</p><ul><li>No certificate is required for a non-secured server.</li><li>No certificate is required when a trusted secure connection is already established.</li><li>A certificate becomes relevant when a secure channel cannot be created.</li></ul></td></tr><tr><td>5</td><td>How can a personal access token be generated inside Tableau?</td><td><p>A personal access token can be created from the Tableau account settings.</p><ul><li>Enter a name for the token and create it.</li><li>Copy and securely store the token value immediately.</li><li>The token value is displayed only once and must be entered in the connection setup form.</li></ul></td></tr><tr><td>6</td><td>How can a cloud-based Tableau environment be distinguished from a server-based environment?</td><td><p>The environment type is mainly identified by the host name entered during setup.</p><ul><li>Server: Usually uses a private domain name or IP address.</li><li>Cloud: Uses a domain configured for cloud access and may use a custom domain name.</li><li>Token-based authentication is recommended for both environments and is mandatory for Tableau Cloud.</li></ul></td></tr><tr><td>7</td><td>What is the Alias Host Name field used for?</td><td><p>The Alias Host Name field is used when the connection address and report-preview address are different.</p><ul><li>The main connection address is used for validation and API calls.</li><li>The alias is used to open and preview reports.</li><li>The alias allows report previews to redirect to the domain normally used for viewing reports.</li></ul></td></tr><tr><td>8</td><td>What does Validate check?</td><td><p>Validate checks only the Tableau sign-in.</p><ul><li>A successful validation means Tableau returned a token.</li><li>A successful validation does not confirm that projects or TWB files are accessible.</li><li>If validation succeeds but crawling returns no content, verify the required View and Download rights, Content URL, or Crawl All Sites configuration.</li></ul></td></tr><tr><td>9</td><td>What does error 401001 or a sign-in error indicate?</td><td><p>A 401001 or sign-in error can occur when the authentication details or site configuration are incorrect.</p><ul><li>Verify the username, password, or personal access token.</li><li>Confirm that the user has access to the specified Content URL site.</li><li>Revalidate the connection after correcting the authentication or site details.</li></ul></td></tr><tr><td>10</td><td>Does the connector modify Tableau content?</td><td><p>No. The connector performs read-only operations against Tableau.</p><ul><li>Signs in to Tableau.</li><li>Lists metadata.</li><li>Downloads XML content.</li><li>Does not publish or delete Tableau content.</li></ul></td></tr><tr><td>11</td><td>Are Owner, Steward, and Custodian Tableau login roles?</td><td><p>No. Owner, Steward, and Custodian are OvalEdge governance roles.</p><ul><li>These roles are used for governance within OvalEdge.</li><li>These roles do not represent Tableau authentication accounts.</li><li>These roles do not sign in to Tableau.</li></ul></td></tr><tr><td>12</td><td>Is the Port field used for Tableau API connectivity?</td><td><p>No. The connection uses the following format:</p><p>https://{host}/api/{version}</p><ul><li>A separate Port value is not used.</li><li>The API version must match the supported XSD.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling" %}

<table><thead><tr><th width="58.83203125">S. No</th><th width="199.59375">Question</th><th width="460.3828125">Answer</th></tr></thead><tbody><tr><td>1</td><td>How is the Tableau structure of site, project, workbook, and view reflected while crawling?</td><td><p>Tableau uses a layered content structure:</p><ul><li>Site: Separate content space.</li><li>Project: Organizes content and controls access; projects can contain sub-projects.</li><li>Workbook: Located within a project and contains one or more views.</li><li>View: Represents a worksheet or dashboard.</li></ul><p>During crawling, the structure is represented as Site + Project → Workbook → View.</p></td></tr><tr><td>2</td><td>What happens when a parent folder is selected for crawling instead of a specific subfolder?</td><td><p>Selecting a parent folder does not automatically crawl all content inside its subfolders.</p><ul><li>The parent folder crawl retrieves reports and data sources directly under that folder.</li><li>Subfolders must remain selected to include their content.</li><li>Subfolders are selected by default unless deliberately turned off before crawling.</li></ul></td></tr><tr><td>3</td><td>What is delta crawling and how does it decide what to bring in?</td><td><p>Delta crawling retrieves only reports that are new or changed since the previous crawl.</p><ul><li>The connector checks the modified date and created date of Tableau reports.</li><li>Only items with a newer date than the previous crawl are retrieved.</li><li>This avoids crawling the entire Tableau environment again.</li></ul></td></tr><tr><td>4</td><td>Why are dashboards, worksheets, and different chart types all shown as the same type in the catalog?</td><td><p>Tableau uses View as the technical term for these content types.</p><ul><li>A worksheet is a view.</li><li>A dashboard is a view containing multiple views.</li><li>Chart types such as bar charts and pie charts are also represented as views.</li><li>The catalog therefore represents these Tableau objects consistently as View.</li></ul></td></tr><tr><td>5</td><td>Why do some column names appear duplicated when looking at a workbook or view?</td><td><p>Column information at the workbook or view level combines columns used across the individual visuals.</p><ul><li>The same column used in multiple visuals appears multiple times.</li><li>Each individual usage is counted rather than merged into one entry.</li><li>This is expected behavior and does not indicate an error.</li><li>Reviewing the specific visual in Tableau shows where the column is used.</li></ul></td></tr><tr><td>6</td><td>Why is validation successful but the crawl returns no content?</td><td><p>A successful validation confirms that sign-in worked, but does not confirm access to Tableau content.</p><ul><li>Verify View and Download permissions.</li><li>Verify the Content URL configuration.</li><li>Enable or verify Crawl All Sites when content from multiple sites is required.</li></ul></td></tr><tr><td>7</td><td>Does the connector download Tableau extracts?</td><td><p>No. Tableau content APIs are called with includeExtract=false.</p><ul><li>Hyper extract files are not downloaded.</li><li>The connector retrieves the required metadata and XML content instead.</li></ul></td></tr><tr><td>8</td><td>Why is source code empty after crawling?</td><td><p>Lineage cannot be built when the required source code is not available.</p><ul><li>Verify that the account has Download rights.</li><li>Recrawl the required reports so the TWB/TDS source code is stored.</li><li>Run the lineage process after the source code becomes available.</li></ul></td></tr><tr><td>9</td><td>Which jobs should be run for Tableau metadata and lineage?</td><td><p>Use the following sequence:</p><ul><li>Validate the Tableau connection.</li><li>Crawl the selected report groups.</li><li>Build Lineage after crawling.</li><li>Do not expect a Profile job for this workflow.</li></ul></td></tr><tr><td>10</td><td>How are Tableau objects mapped in OvalEdge?</td><td><p>Tableau objects are mapped as follows:</p><ul><li>Site + Project → Report Group</li><li>Workbook / DataSource → Report</li><li>View/Dashboard → Report (Sub-report)</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Lineage" %}

<table data-search="true"><thead><tr><th width="58.62890625">S. No</th><th width="200.3671875">Question</th><th>Answer</th></tr></thead><tbody><tr><td>1</td><td>What is a semantic table and why does it appear in lineage?</td><td><p>A semantic table represents how a Tableau data source is built.</p><ul><li>It can represent a direct table connection, custom SQL combining multiple tables, a file, or another combination.</li><li>It provides an accurate representation when the data source is not a one-to-one copy of a source table.</li><li>The semantic table is temporary and represents the data-source structure only.</li><li>It does not exist as an actual object in the original source system.</li></ul></td></tr><tr><td>2</td><td>Why does an inline data source not appear as a separate item in the catalog?</td><td><p>An inline data source is embedded directly inside a workbook rather than published separately.</p><ul><li>Published data source: Appears as a separate catalog item and can be reused across workbooks.</li><li>Inline data source: Exists only within the workbook and does not appear separately in the catalog.</li><li>During lineage creation, a temporary object represents the embedded data source so the lineage remains complete.</li></ul></td></tr><tr><td>3</td><td>Does crawling build lineage automatically?</td><td><p>No. Crawling and lineage are separate processes.</p><ul><li>The crawl stores the Tableau XML content.</li><li>The lineage job reads the stored source code.</li><li>Run the lineage job after the crawl to build lineage.</li></ul></td></tr><tr><td>4</td><td>How does lineage work for Tableau Hyper reports?</td><td><p>Tableau Hyper reports use saved data extracts rather than live database connections.</p><ul><li>OvalEdge creates a temporary stand-in table for the Hyper data source.</li><li>The temporary table is connected to the Tableau report in lineage.</li><li>The original database tables, such as Snowflake or MySQL, are not connected back to the Tableau report.</li><li>Hyper report lineage is therefore partial and does not show the complete path to the original database.</li></ul></td></tr><tr><td>5</td><td>What is the difference between Hyper and non-Hyper lineage?</td><td><p>Hyper reports:</p><ul><li>Use saved extracts rather than live database tables.</li><li>Use a temporary table in OvalEdge.</li><li>Provide partial lineage only.</li></ul><p>Non-Hyper reports:</p><ul><li>Can use live tables, files, or SQL.</li><li>Can usually connect the real source to the Tableau report.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# 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.ovaledge.com/release7.2/connectors/connector-repositories/reporting-tool/tableau.md?ask=<question>&goal=<endgoal>
```

`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.