Does Collibra create a new asset when a Tableau Workbook is renamed on the Tableau Server?
Summary: Fatima Rodriguez inquired about how Collibra handles renamed Tableau Workbooks, noting inconsistencies where sometimes a new asset is created while other times the existing asset is updated. Jolly Lara suggested that this behavior might depend on how Collibra matches assets during synchronization, influenced by source identifiers. They recommended checking integration configurations and synchronization logs and advised consulting Collibra documentation or experts for clarification on this behavior.
I was wondering whether anyone know if Collibra creates a new asset when a Tableau Workbook is renamed on the Tableau Server or if the asset is simply updated?
Our team renamed a workbook in Tableau and witnessed how Collibra created a new asset with the recently updated name, while the old one was marked as "Missing From Source". However, we've recently noticed that when we've renamed workbooks Collibra has been simply updating the same asset without creating a new one.
Would anyone be able to confirm what is the expected behavior for Collibra updating renamed Tableau assets and share any documentation.
Thanks!
Jolly Lara
·yesterday at 9:15 AMFrom what I understand, the behavior can depend on how the Tableau integration identifies and matches assets during synchronization. If Collibra uses a stable source identifier for the workbook, a rename may simply update the existing asset. If that identifier changes or the synchronization cannot match the renamed workbook to the previous asset, Collibra may create a new asset and mark the previous one as missing from the source.
I would check the integration configuration, synchronization logs, and the source identifiers associated with both workbooks. Comparing the metadata before and after the rename may also help determine why the behavior differs between cases.
I have also seen unrelated discussions where people pay someone to take online class, but that is obviously separate from this Collibra issue. For this case, the most useful confirmation would probably come from Collibra documentation covering Tableau asset matching and synchronization behavior, or from someone who has worked directly with the connector.