Power BI currently exposes dataset‑level lineage and model metadata, but does not expose visual‑level field/table usage anywhere.
Tools like Measure Killer, Power BI Cleaner, RADACAD Clean‑up, Bravo, DAX Studio, or the Admin Scan API can determine usage only by combining model dependencies—NOT pure visualization usage.
This makes it impossible to:
- Identify which tables/columns are used only by visuals
- Determine which fields can be safely removed from the model
- Audit visual dependencies accurately in large shared‑dataset (thin report) deployments
Request:
Please change the way metadata is stored in power bi to be able to get
- Visual‑level field usage
- Which tables/columns are used by visuals, filters, and slicers
- A “visual dependency map” that excludes model-level DAX/relationships that are not used in visualizations.
This would drastically improve governance, dataset optimization, and report maintenance across enterprise deployments.
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections
on:
Need more details on Average utilization% in Capac...
lbendlin
on:
Increase the 1,000 Item Limit per Fabric Workspace
NaamaTsafrir
on:
Rename "Domain Admin" to "Domain Owner" to match P...