Overview Tableau integration steps

The Tableau integration enables you to harvest Tableau metadata and create new Tableau assets in Data Catalog. Collibra Data Intelligence Cloud analyzes and processes the metadata and presents it as specific asset types, retaining their original names.

Steps

The table below shows the steps and prerequisites required to integrate Tableau in Collibra via the lineage harvester.

Step	What?	Description	Prerequisites
1	Set up Tableau.	Before you start the Tableau integration in Data Catalog, make sure that the lineage harvester can reach the Tableau metadata. Perform these tasks before you start the actual Tableau ingestion process. Warning Because these tasks are performed outside of Collibra, it is possible that the content changes without us knowing. We strongly recommend that you carefully read the source documentation.	You have a Tableau subscription.
2	Create a new domain.	Before you can ingest Tableau metadata, you have to create a new domain or choose an existing domain to store the new Tableau assets. Warning If you are using Collibra Data Intelligence Cloud 2021.11 or older, you have to add all Tableau attributes in the operating model to a scope and create a scoped assignment before you ingest Tableau via the lineage harvester. For complete information and step-by-step instruction, see Tableau general troubleshooting.	You have a resource role with the following resource permissions: Domain: Add
3	Prepare the physical data layer.	You prepare Data Catalog's physical data layer to enable Data Catalog to automatically stitch the Tableau assets to existing assets in Data Catalog. Important In the global assignment of each asset type included in the Tableau operating model, ensure that none of the characteristics that are in the operating model have a maximum cardinality of “0”. If the maximum cardinality is set to “0” for any such characteristics, ingestion will fail.	You have a global role with the Catalog global permission, for example Catalog Author. You have set up the JDBC driver of your source data, for example Snowflake. You have a resource role with the following resource permissions on the Schema community: Asset > add Attribute > add Domain > add Attachment > add You have the permissions to retrieve the metadata of the following database components through the JDBC Driver Database Metadata methods: Schemas Tables Columns
4	Download and install the lineage harvester	You use the lineage harvester to trigger the creation of Tableau assets, their relations and a technical lineage in Data Catalog. You can download the lineage harvester from the Collibra Product Resource Downloads page.	Your environment meets the system requirements to install and use the lineage harvester.
5	Prepare the lineage harvester configuration file and run the lineage harvester.	You create a lineage harvester configuration file with Tableau connection information and run the lineage harvester to import the results of the Tableau integration and the technical lineage for Tableau into Data Catalog. As a result, Collibra creates new Tableau assets in Data Catalog and imports relations between these assets. It also creates a technical lineage for Tableau assets and other data sources in the lineage harvester configuration file.	Set up the latest lineage harvester. Test your connectivity with the Tableau server. Prepare the Data Catalog physical data layer for technical lineage. Create one or more BI Data Catalog domains in which you want to ingest the Tableau assets. Collibra Data Intelligence Cloud. A global role with the following global permissions: Catalog, for example Catalog Author Data Stewardship Manager Manage all resources System administration Technical lineage A resource role with the following resource permission on the community level in which you created the BI Data Catalog domain: Asset: add Attribute: add Domain: add Attachment: add
6	View the Tableau assets and technical lineage	After the Tableau metadata is ingested in Data Catalog, you can go to the domain where you ingested Tableau and see the list of ingested Tableau assets. These assets are automatically stitched to existing assets in Data Catalog. You can also view the Tableau technical lineage. Warning When you run the lineage harvester, Collibra Data Lineage creates all Tableau assets in a single BI Catalog domain. We highly recommend that you do not move these assets to another domain. If you move assets to another domain, they will be deleted and recreated in the initial BI Catalog domain when you synchronize Tableau. As a consequence, all manually added data of those assets is lost.	You have a Data Catalog global role with the Catalog and Technical lineage global permissions.

Naming convention

When you synchronize Tableau, Collibra follows a strict naming convention for the names of the new assets. Each asset has a display name and full name. The full name represents the asset path from asset to the database it belongs to. You can freely edit the display name. However, you should never edit the full name, because Data Catalog may need it to synchronize and stitch data sources. This may cause unexpected results and break the synchronization process.

Warning We strongly recommend that you not edit the full names of any Tableau assets. Doing so will likely lead to errors during the synchronization process.