Power BI lineage view vs field-level lineage
Power BI's built-in lineage view and impact analysis answer item-level questions well. Questions about a particular column or measure need field-level lineage. Here is what each one shows.
Lineage view shows the relationships between the items in a workspace and their external dependencies.1 Impact analysis, opened from a semantic model, shows how many workspaces, reports and dashboards might be affected by a change.2 TrailsBI reads the project files and follows each column and measure to the visuals that use it.
Where Power BI's lineage view is stronger
- It shows what is actually published, live, in the service, with no files to export.
- It covers every item type in a workspace, including dataflows, dashboards and other Fabric items, not just semantic models and reports.
- Impact analysis includes usage: unique visitors and views on the affected items over the last 30 days.
- It can notify contacts of the affected items about a change.
Where TrailsBI helps
- It goes below the item. Columns, measures, visuals and pages, not just which reports use a model.
- No permissions needed. Impact analysis needs write permission on the model; lineage view needs a Pro licence and a Contributor role or above. TrailsBI reads files.12
- Across workspaces. Impact analysis can't analyse a semantic model shown in lineage but located in another workspace. TrailsBI joins reports to their models across all the workspace folders you give it.
- Before you publish. It checks the change in your project, so broken visuals are found before anyone opens a report.
“I am looking for table and column specific lineage, which I have not been able to find. I understand that I can do this manually by going through each and every report, but was hoping that there is a tool to show where tables and columns are used, not just models.”
"Semantic model column lineage", Fabric Community, November 2024. Read the thread
Side by side
| TrailsBI | Power BI lineage view | Source | |
|---|---|---|---|
| Level of detail | Data source, table, column, measure, visual, page | Items: semantic models, reports, dashboards and other workspace items | Data lineage |
| What a change affects | The visuals and pages that use the field | How many workspaces, reports and dashboards might be affected | Impact analysis |
| Permissions | None, reads project files | Pro licence and Admin, Member or Contributor role; write permission for impact analysis | Data lineage |
| Models in other workspaces | Joined, if you give it their folders | Impact analysis has to be run from the model's own workspace | Impact analysis |
| Usage data | None | Views and unique visitors over 30 days | Impact analysis |
| What it reads | Power BI project files (PBIP) on your machine | What is published in the service | Data lineage |
Questions
Does Power BI have column-level lineage?
Not in the lineage view, which works with items such as semantic models, reports and dashboards. Microsoft Purview can show column-level lineage inside Power BI semantic models only when the source is Azure SQL Database.
Why can't I open lineage view?
Microsoft says you need a Power BI Pro licence and an Admin, Member or Contributor role in the workspace. Users with the Viewer role can't switch to lineage view.
Should I use both?
Yes. Use the service's lineage view and impact analysis for what is published and who uses it, and field-level lineage to see which visuals depend on a field before you change it.