Troubleshooting

Warning The end of life of Jobserver and all related Jobserver integrations has been announced for September 30, 2024. This means that the Tableau via Jobserver integration method is deprecated and will also reach its end of life on September 30, 2024. To integrate Tableau metadata and create lineage, please use Edge or lineage harvester.

The following table contains the most common issues that you can encounter while ingesting or synchronizing Tableau.

Issue	Solution
Tableau images are not fetched correctly	Synchronizing means refreshing the assets that are currently in Data Catalog as a result of a previous ingestion or synchronization job. After synchronizing Tableau, the assets in Data Catalog accurately reflect the metadata as it exists at the time of synchronization. Images such as report thumbnails are not downloaded and stored in Data Catalog. Instead, Data Catalog stores a link to the image. Every time you open the asset page, the image is fetched from Tableau. Images are not fetched correctly if there is a problem with this link. A common issue is caused by the base URL parameter, which is part of the link. If the base URL is not set correctly in Collibra Console, the links to the Tableau images are broken. To fix this issue, edit the base URL in Collibra Console.
When you synchronize a Tableau Server 2020.2, some Tableau data is skipped.	In most cases, this occurs when people are actively using Tableau while Data Catalog is synchronizing the Tableau Server. The technical reason is that the APIs collect Tableau data at different times. If users make changes in Tableau, the data that is collected by the APIs may be inconsistent. When that happens, the corresponding assets are not synchronized in Data Catalog. We highly recommend that you synchronize Tableau after working hours. This reduces the chance that Tableau data is added, changed, renamed or deleted on Tableau's side during the synchronization process.
Tableau synchronization fails with error message `Duplicate key`.	The Tableau synchronization fails with the `Duplicate key` error when you have multiple views with the same name in the same workbook. To solve this problem, we highly recommend to give each view in Tableau a unique name before you synchronize the Tableau Server in Data Catalog.
When you integrate Tableau, relations between Tableau Data Attributes and Tableau Report Attributes are not being created.	The likely issue is that the report is using embedded data sources or custom SQL. If that is the case, we recommend that you switch to the new Tableau integration method, via the lineage harvester, which supports embedded data sources and custom SQL.