Tableau Lineage Integration
Summary: Heather Fara, Heather Fara, shared challenges with integrating Tableau Server 2025.1.3 and Collibra 2025.11, specifically in stitching lineage. Despite efforts such as granting the Server Admin role, adjusting settings, and using Tableau's tools for field names, the lineage integration ends up with thousands of items in the "unused" bucket without proper linkage. Heather Fara expressed frustration over the lack of resolution from support, noting limitations in scoping ingestion and disappointing results from submitting tickets. Additionally, Heather Fara alludes to larger issues, such as problems with link servers in stored procedures, expressing dissatisfaction with current lineage capabilities.
We are able to connect to Tableau Server 2025.1.3 to Collibra 2025.11 and read in the data, but our attempts to stitch lineage have failed.
Despite granting the Server Admin role (super user) in Tableau Settings we also checked:
Automatically grant authorized user access to metadata about databases and tables
Sensitive Lineage > Show complete lineage (default)
Turn on Tableau Catalogue
We also added the service account to the project, just in case.
The result is thousands of items listed in Technical Lineage in the "unused" bucket with zero lineage.
I understand that names of field can't change for Collibra, but 100% of field names have been changed in Tableau, using Tableau's automated ingestion tools which gives fields human readable Field names. This information is stored in a table in Tableau. The matching database column name is the "Remote Field Name" and the "Field Name" is effectively the masked name.
What am I missing? Is there a property to add to the config file?
Heather Fara
OP4 months agoOK, as I understand there was something wrong with the connector and it was looking for linkages and the number of linkages was zero...creating too many errors while reading. Collibra fixed something ans it working now. More information to come I am told.
That said I wanted to share that the big issue is the Edge connector doesn't have a native way to restrict ingestion to a set of projects (with subprojects and asset related. This was very simple in lineage harvestor and a missing capability that would have also fixed out issed because it would not me running over so many assets and racking up errors on injestion. We are working in dev to develop the code to do this in edge, so if you are looking for it - will will have it sorted very soon. It should be fairly similar for Power Bi.
Heather Fara
OP4 months ago · EditedNo resolution. It has nothing to do with remote field names, it handles them very well.
Edge doesn’t have a way to scope ingestion based on a property like project. Our site has too many objects only a couple stitch, so it stops reading after a couple projects due to a high count of unused assets, as l understand. This is a Lineage killer. It was easy to scope injection by project, prior to edge.
If someone knows how to add properties or restrict read for the tableau lineage capability or has another suggestion, we put a ticket in and got no resolution after a month of pressing.
It was reading more after they did something, but they said they did nothing. Despite another month of asking what tests they ran that might have unstuck things either…we go zero response.
l can’t recommend lineage right now.
This is one of three major issues. Link servers referenced in stored procedures is even worse, and the best we can do at this point is hand code everything in the deprecated lineage harvester.