How to identify used vs. unused columns in a Fabric semantic model without third-party tools?

[Nazdac2024]

Hi everyone,

I’ve been asked to analyze our data model with a special focus on identifying which columns are used and which are unused.

Because of company restrictions, I can only rely on DAX Studio, Bravo, and Tabular Editor (no other third-party tools).

For me, a “used” column means:

• Referenced in measures

• Part of relationships

• Used in visuals or filters (page/report level)

• Appearing in Power Query ETL steps

I’d love to hear: how can I best approach this analysis with the tools I have?

P.S. I’m not a full-time Power BI developer—more of a Power BI end user—so any practical guidance would be much appreciated 🙂

Thanks!

[Brunner_BI]

The previous comments are mostly AI generated and unfortunately not accurate.

The only tool that can do this is Measure Killer. You would have to get it approved in your company though...

There is absolutely no way to do it using the other tools mentioned because they only search the data model and not any connected reports (visuals, filters etc.).

[v-ssriganesh]

Hi @Nazdac2024 ,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @rohit1991 & @rajendraongole1 for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

Thank you for being part of the Microsoft Fabric Community.

[rajendraongole1]

Hi @Nazdac2024  -can you try tabular editor,  it can search across all measures, calculated columns, and calculated tables for references.

Tabular Editor 2.x | TabularEditor

Hope this helps.

[rohit1991]

Hi @Nazdac2024 

Could you please try below steps:-

1. DAX Studio >>VertiPaq Analyzer >> Columns
   Filter Is Unused = True (optionally also not in relationships / hierarchies / sort-by). Export this as your candidate list.

2. Tabular Editor >>Find Where Used
   For each candidate column, check dependencies. If nothing references it, hide it first (IsHidden = true). BPA rules can help spot stragglers.

3. Bravo >>Analyze Model
   Confirm “Unused” and check column size to prioritize what to drop.

Heads-up

• These tools only see model usage, not what separate report pages might use.

• Hide first, ask report owners to sanity-check, then remove in Power Query.