Why impact analysis can't tell you which visuals will break
Power BI's impact analysis counts the reports and dashboards a change might affect. It can't tell you which visuals use the field you are about to rename. Here is why, and how to check before you publish.
Impact analysis is the closest thing Power BI has to a "what breaks if I change this" button. Open it from a semantic model and it tells you how many workspaces, reports and dashboards might be affected, and how many people viewed them in the last 30 days.1 That is useful for deciding who to warn. It is not enough for deciding whether a change is safe.
What impact analysis actually shows
Microsoft's documentation is precise about it. Impact analysis shows counts of potentially affected items and their usage. You need write permission on the model to run it, and you can't run it on a semantic model that lineage view shows but that lives in another workspace: you have to go to the source workspace.1 The lineage view it builds on works with whole items, such as semantic models, reports and dashboards, not with tables, columns or visuals.2
So for a model with forty reports on it, impact analysis answers "forty reports might be affected". It can't say that three visuals on two pages use the measure you are renaming and the other thirty-seven reports never touch it.
Why that matters for renames
Reports refer to fields by name. Rename a measure, and every live-connected report that uses it asks for the old name and shows "Something's wrong with one or more fields". Microsoft's answer in a long-running forum thread is that this is by design:3
“By design. … Model changes like rename don't flow out to all the reports that could have been created off of them.”
Microsoft, via Community Support, Fabric Community, 2020. Read the thread
Without a field-level answer, teams fall back to opening reports one by one, exporting usage to Excel, or renaming and waiting for complaints. Marc Lelijveld describes the export-and-analyse route in detail, and calls the built-in view incomplete for this job.4
How to check fields before you publish
Field-level impact needs the report definitions, not just the item graph. Power BI projects (PBIP) store each report's visuals and the fields they use as files, so a tool can read them:
- Save the model and its reports as Power BI projects, or use the Git folders your workspaces sync to.
- Before the change, look up the field and list every visual and page that uses it.
- Make the change, then check again for visuals that refer to a name the model no longer has.
That is what TrailsBI does with the Lineage view and the "Fields missing from the semantic model" check, offline and without write permission. Use it together with impact analysis: TrailsBI tells you which visuals change, impact analysis tells you who uses them.