> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tableau FAQ

> Common questions about connecting Tableau to Prizm, authentication, asset selection, lineage, and quality propagation.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Tableau FAQ",
            "description": "Common questions about connecting Tableau to Prizm, authentication, asset selection, lineage, and quality propagation.",
            "url": "https://docs.dqlabs.ai/sources/tableau/faq",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## Connection & Authentication

<AccordionGroup>
  <Accordion title="Which authentication method should I use?">
    **Connected Apps with Direct Trust** is the recommended method for all environments. It uses OAuth-based authentication without requiring a user password and is the most secure and debuggable option.

    | Method                        | When to Use                                                                                   |
    | :---------------------------- | :-------------------------------------------------------------------------------------------- |
    | Connected Apps (Direct Trust) | Recommended. Tableau Server 2023.3+ or Tableau Cloud. Requires Site Admin Creator role.       |
    | Personal Access Token         | Use when Connected Apps is not available. Longer-lived credential — requires manual rotation. |
    | Username / Password           | Legacy fallback. Not recommended for production. Broader access scope.                        |
  </Accordion>

  <Accordion title="What Tableau role does the connecting user need?">
    For Connected Apps authentication, the user must have at minimum **Site Admin Creator** privileges. Site Admin Explorer may work in some environments but has caused connectivity issues in others. The user must have access to the Metadata API and REST APIs.
  </Accordion>

  <Accordion title="Can I connect to both Tableau Cloud and Tableau Server?">
    Yes. Prizm supports both deployment types. Create a separate connector for each deployment. For Tableau Cloud, ensure the HTTPS scheme is included in the host URL — Tableau Cloud does not support HTTP for Metadata API access.
  </Accordion>

  <Accordion title="How do I find my Tableau site name?">
    Inspect the Tableau URL in your browser. The site name appears after `/site/` in the URL path:

    * `https://prod-uswest-b.online.tableau.com/#/site/staging/projects` → site name: `staging`
    * `http://techdata.io/#/site/AnalyticsTeam/projects` → site name: `AnalyticsTeam`

    Site name is **case-sensitive** and must match exactly. If your environment uses the Default Site, leave the Site Name field blank.
  </Accordion>

  <Accordion title="What happens when a Personal Access Token expires?">
    Personal Access Tokens must be manually rotated in Tableau (**User Settings → Access Tokens**) and updated in the Prizm connector settings. Tableau does not auto-refresh PATs. Connected Apps authentication is recommended to avoid manual rotation.
  </Accordion>
</AccordionGroup>

## Asset Selection & Scoping

<AccordionGroup>
  <Accordion title="Can I connect specific workbooks rather than all workbooks?">
    Yes. During setup, Prizm presents a list of all available workbooks in the configured site. Use checkboxes to select exactly which workbooks to bring into Prizm. You can add or remove workbooks at any time from the connector asset selection page.
  </Accordion>

  <Accordion title="How do I handle workbooks that are deleted in Tableau?">
    Use the **Sync** action from the connector asset selection page. Sync detects workbooks that have been deleted in Tableau and automatically marks the corresponding assets as deprecated in Prizm. Deprecated assets are retained in the catalog for historical lineage and audit purposes.
  </Accordion>

  <Accordion title="Are Tableau Flows and Metrics supported?">
    Tableau Flows are captured in the data model (TableauFlow object) but full Flow observability is not currently in scope for the connector. Tableau Metrics (the native Tableau Metrics feature) are deprecated by Tableau and are not ingested by Prizm.
  </Accordion>

  <Accordion title="Can I connect to multiple Tableau sites in the same workspace?">
    Create a separate connector for each site. Each connector has its own credentials, site name, workbook selection, and job schedules.
  </Accordion>
</AccordionGroup>

## Lineage

<AccordionGroup>
  <Accordion title="How does Prizm build lineage from Tableau?">
    Lineage is auto-inferred from the `upstreamTables` and `upstreamColumns` declared in the Tableau datasource metadata (via the Metadata API). Prizm stitches this with the warehouse-side lineage from Snowflake or Databricks to produce an end-to-end graph:

    **Warehouse table → Published Data Source → Worksheet → Dashboard**

    Column-level lineage (which warehouse column maps to which Tableau field) is also available where Tableau datasource fields declare upstream column references.
  </Accordion>

  <Accordion title="Can I manually map lineage if auto-inference is incomplete?">
    Yes. From the Lineage tab on any Tableau asset, you can manually map upstream or downstream assets by selecting the required asset names from the dropdown. Manual lineage mappings are preserved across catalog syncs.
  </Accordion>

  <Accordion title="How long does lineage take to appear after setup?">
    The Catalog job runs immediately after the connector is saved. Lineage data is available within a few minutes for most environments. End-to-end stitching with warehouse-side lineage may take up to 24 hours due to batching.
  </Accordion>
</AccordionGroup>

## Observability & Freshness

<AccordionGroup>
  <Accordion title="How does Prizm monitor Tableau freshness?">
    Prizm tracks the `last_successful_refresh_time` for each Tableau extract via the Extract Refresh Tasks API (REST). The freshness threshold is calculated dynamically:

    **Expected Range = (expected refresh interval − last successful refresh time) ± 3 × average execution time**

    This means the threshold automatically adjusts to your extract schedule. You can also set a manual threshold if you need a fixed SLA window.
  </Accordion>

  <Accordion title="What refresh job signals does Prizm monitor?">
    The Operational/Refresh job (runs hourly) tracks: freshness delay, refresh success rate, consecutive failures, and p95 refresh duration. Only extract refresh tasks and related background jobs are monitored — permission jobs, subscription sends, and thumbnail generation are excluded.
  </Accordion>

  <Accordion title="Can Prizm detect zombie dashboards?">
    Yes. Usage metrics (hits\_last\_14d, hits\_last\_30d, hits\_last\_90d, hits\_last\_365d) are collected daily. Workbooks with no views in 90+ days can be flagged for deprecation review. The usage-weighted health score also surfaces high-traffic workbooks with quality issues first.
  </Accordion>
</AccordionGroup>

## Quality Propagation

<AccordionGroup>
  <Accordion title="How does quality propagation work?">
    When propagation is enabled, Prizm automatically links the quality state of upstream warehouse tables to the Tableau workbooks that consume them. When an alert fires or an issue is created on a warehouse table, the signal propagates downstream to every Tableau workbook that queries that table.

    Propagation is configured per signal (Alerts, Issues, Score) and can be set to **Based on associated table** or **None**.
  </Accordion>

  <Accordion title="What is the difference between score propagation and Data Quality Warnings?">
    **Score propagation** surfaces upstream table quality scores inside Prizm on the Tableau workbook asset page — visible to Prizm users.

    **Data Quality Warnings** push a warning directly into Tableau Server or Tableau Cloud, where it appears on the Tableau Data Source and overlays on views consuming it — visible to all Tableau users regardless of Prizm access. DQ Warnings require Tableau Enterprise or the Data Management add-on.
  </Accordion>

  <Accordion title="Data Quality Warnings are not appearing in Tableau — why?">
    Check the following:

    1. Your Tableau license includes Data Quality Warnings (Tableau Enterprise, Tableau+, or Data Management add-on purchased before September 16, 2024)
    2. Tableau Catalog is enabled on your instance
    3. Warnings apply only to **Tableau Data Sources** — not to Workbooks or Views directly
    4. Warnings expire approximately 24 hours after being set — re-apply if needed
    5. The Prizm user has sufficient permissions to write DQ warnings to the Tableau site
  </Accordion>
</AccordionGroup>

## Connector Lifecycle

<AccordionGroup>
  <Accordion title="How often does Prizm sync metadata from Tableau?">
    | Job                   | Schedule                             |
    | :-------------------- | :----------------------------------- |
    | Catalog / Metadata    | Daily (or on-demand after a publish) |
    | Operational / Refresh | Hourly                               |
    | Usage / Adoption      | Daily                                |

    Schedules can be overridden from the connector detail page.
  </Accordion>

  <Accordion title="What happens if a connector is paused or deleted?">
    **Paused**: Existing metadata, scores, and propagated signals are retained. No new data is collected until the connector is re-enabled.

    **Deleted**: Once approved through the deletion workflow, the connector and all associated metadata are permanently removed. This action cannot be undone.
  </Accordion>

  <Accordion title="A Tableau asset is missing in Prizm — how do I troubleshoot?">
    Check the following:

    1. Confirm the workbook is selected in the connector's asset selection list
    2. Verify the Tableau user has permission to see the workbook (Prizm respects Tableau permissions)
    3. Check that the Catalog job has completed at least one successful run — go to **Settings → Sources → Logs**
    4. If the workbook was recently published, trigger an on-demand Catalog sync
    5. If the issue persists, contact Prizm Support
  </Accordion>
</AccordionGroup>

***

For connection errors and authentication issues, see the [Troubleshooting page](/help/troubleshooting). For definitions of terms used in this FAQ, see the [Glossary](/help/glossary).