Matia Now Connects to Power BI for Source-to-Dashboard Lineage

Today, Matia is adding Power BI to the Catalog, extending the same lineage, descriptions, and usage tracking that already covers Metabase, Tableau, Omni, and Hex to Microsoft's BI platform too.

Power BI organizes everything into workspaces of datasets, reports, and dashboards. It's usually the last stop before a number turns into a decision. Until Matia, that's also where lineage stopped.

The Challenge: No Lineage Into Power BI

Most teams can point to a dashboard. Fewer can say, on demand, which table it came from or what happened if that table changes.

• Even when lineage exists, it usually stops at the warehouse. It can't tell you which column in that table actually feeds the field breaking on the dashboard.
• Business teams trust what's on screen. Nobody questions a chart until a number looks wrong.
• Once that happens, someone has to trace it back by hand: Power BI to the warehouse, the warehouse to whatever fed it, one Slack message at a time.
• The more people plug into Power BI, the bigger that gap gets. It doesn't shrink with scale. It compounds making finding mistakes more costly and time consuming.

What We Built

Once you connect Power BI, Matia's Catalog picks up:

→ Descriptions: Asset descriptions from Power BI carry over too, so nobody has to redocument what a report already explains.

→ Lineage: Native Power BI lineage traces the relationships between datasets, reports, and dashboards down to the column level, running upstream through Snowflake and Databricks so you can follow a single column back to where it started.

→ Usage: Usage metrics from Power BI land in the Catalog's usage tab, so you can see what's being read, not just what exists.

Power BI Joins Matia's Growing List of BI Connectors

Power BI is adding to the growing list of BI connectors in Matia's Catalog, joining Metabase, Tableau, Omni, and Hex. Power BI is here for the same reason Hex and Omni are: teams don't run one BI tool, so the Catalog doesn't assume they do.

Most catalog tools start lineage at the table that lands in the warehouse. Matia already sits upstream of that, in ETL, so lineage traces accurately past the warehouse, all the way to the source system a number started in.

How Teams Are Using It

Data engineers get a direct answer to what breaks if they change a table, without tracing it through Power BI by hand first.

Analytics engineers stop being the default translator between what a report shows and what happened in the warehouse.

Business stakeholders can trust a Power BI dashboard because the lineage behind it is provable, not just claimed.

Available Now

Power BI support is live. If you're already on Matia, connect your Power BI workspace from the Catalog, and descriptions, lineage, and usage start appearing automatically.

Book a demo to see lineage into Power BI and our other BI tools in action.