Limitations and Troubleshooting

Limitations

  • Personal access token can only be used for a single metadata extraction. If the token is used for multiple extractions in parallel, only the first extraction will work; for others an authentication error message will be displayed.

  • If Permission Mirroring and Preview features are enabled, they are expected to considerably increase the Metadata Extraction job duration.

  • Metadata Extraction will fail if the Tableau Metadata APIs are re-indexing post the Tableau instance upgrade.

  • Column Sampling may not fully extract the column sample data of all the views. The connector tries to match the CSV headers from Tableau Rest API with the column metadata received from the graphQL query response. If a column name does not have a corresponding CSV header, the data will not be extracted.

  • Cross-System Lineage is not supported for data sources created from HYPER (.hyper) files. The database hostname and/or port information is not returned from Tableau Metadata API for such data sources.

  • Cross-System Lineage is not supported for data sources created using Oracle synonyms due to an API limitation from Tableau.

  • If there are projects with the same name in a site, there can be wrong mapping of parent projects for datasources in such projects.

  • If Site specific MDE for Personal Access Token with Tableau Server is used in connector version prior to 1.9.0 and if you upgrade the connector to 1.9.0 and newer; Tableau Cloud will be selected by default and user need to select Tableau Server manually.

  • In Alation, published data sources will be displayed only in the Data Sources tabs at the project and report levels. They will not be shown in the data sources tab at the workbook level.

    • In Alation, published data sources always have the project as the parent folder, while unpublished data sources have the workbook as the parent folder.

    • For each workbook that uses a published datasource, Tableau automatically creates an embedded datasource, allowing users to perform additional data modeling within Tableau.

    • In Alation, the auto-generated embedded data sources are cataloged at the workbook level based on the information provided by the Tableau metadata API response.

    • To prevent cataloging the auto-generated embedded data sources at the workbook level, turn off the Extract auto-generated embedded data sources toggle in the Connector Settings section.

    • For example, a published datasource in a report will be visible at both the report and project levels in Alaton. However, you will see auto-generated embedded data sources at the workbook level.

      • Project Level:

      ../../../_images/Published_Project_sample.png

      • Report Level:

      ../../../_images/Report_using_published_ds.png

      • Workbook level:

      ../../../_images/Workbook_using_published_ds.png

Troubleshooting

Refer to Troubleshooting.

Type of Error

Reason

Solution

NODE_LIMIT_EXCEEDED

Connector logs show this message: Showing partial results. The request exceeded the ‘n’ node limit.

Either organize your projects and wokrbooks in a more optimized or increase the node limit on Tableau server.

ApolloNetworkException

When a request takes longer than the configured timeout in seconds.

Increase the Request timeout in seconds input field in the Additional Settings section from default 20 to a higher value.

BACKFILL_RUNNING

Still creating the Metadata API Store. Results from the query may be incomplete at this time.

Wait for the process to complete.