Identify unused tables/ columns

[lars_schreiber]

With growing data models and 10s or 100s of measures its hard to keep the overview wich of the columns are neither used in a measure, nor as a slicer/ filter. For optimizing the data model (e. g. removing unnecessary columns) it would be great to know who they are.

[fbcideas_migusr]

Would also be great to have a list of where calculated measures/columns are used in the report.

[m_webb]

This would be a perfect feature to add to the main application or as an ofshoot application that could scan your file and produce a quick report of unused measures/calc columns. i wonder if its possible for a 3rd party application to do this?

[JanVW]

Great idea! Would love to have a model optimizer that removes unused columns etc. 🙂

[jorge-mena_saut]

This would super useful for cleaning the data model o just to see what measures are necessary and not. Maybe a Highlight tool would be great in the relationship view or in the report view.

[peter_j_pran]

I love this, was about to add a similar idea. This would help the cleanup work immensly.

[paulmall]

This would be a real time-saver.

[james_mccahill]

This would be very effective in improving performance

[lars_vanpelt]

This would be a great way of informing what code can be removed from SQL queries on established reports without having to go through every single visual.

[eitanl]

Great and important idea. can make the report much more efficient. also, if possible, to mark unused column also (can be later manually deleted from the module in order to improve the report process result )

[rlovely]

Totally agree with this and other suggestions for managing measures, identifying dependencies and so forth. I create a lot of interim and/or 'experimental' measures during report development and it would be nice to quickly identify the measures I end up not using when I'm ready to share my final reports