Expand IBM Manta / IKC metadata harvesting support to cover PBIP (Power BI Project) format and additional Tableau file formats (.hyper, .tde, .twbr)

IBM Manta and IKC currently support metadata harvesting and lineage stitching for Power BI .pbix files and Tableau formats .twb, .twbx, .tds, .tdsx. Two gaps were identified during a client engagement with Bradesco (Brazil):

1. Power BI — PBIP format IBM Manta and IKC already support metadata harvesting and lineage stitching for Power BI .pbix files. However, Microsoft has introduced the Power BI Project format (.pbip), a folder-based, Git-friendly structure designed for versioning and collaborative development, positioned as the future standard for Power BI Desktop. During a client engagement, Bradesco confirmed they are actively migrating parts of their BI environment to PBIP due to native GitHub/versioning integration, and explicitly requested that IBM extend the existing PBIX support to also cover PBIP during their transition period.

Requested additional capabilities for PBIP:

• Metadata harvesting into IKC/watsonx.data
• Column-level lineage stitching in IBM Manta
• Governance artifact association (business terms, data classes, sensitive data classification) consistent with current PBIX behavior

While .pbip and .pbix are technically interconvertible, requiring manual conversion defeats the purpose of the newer format and introduces friction in CI/CD pipelines.

2. Tableau — additional file formats The client also uses Tableau internally and referenced the following formats as relevant to their environment: .hyper, .tde, .twbr. Current support covers .twb, .twbx, .tds, .tdsx — leaving these three formats without harvesting or lineage coverage.

Requested capabilities for the additional Tableau formats:

• Metadata harvesting into IKC/watsonx.data
• Lineage stitching in IBM Manta where applicable
• Governance artifact association (business terms, data classes, sensitive data classification) consistent with currently supported Tableau formats