Column visibility , depends on the criteria there should be an option to show/hide column on table.
merged ideas 1 Merged Idea
Needs Votes

This feature would be a game-changer.

Often a drill through/down requires a "key" column for the related records. It would be great to be able to have a feature whereby you could add the key as a hidden column on visuals, purely so that they can be used when drilling through to related records/reports. At the moment you must show any fields in a visual where you want to drill from, and having to have a key column not only takes up space, but for the end user is meaningless.

Would be nice to be able to have a hidden column in grid used to sort the grid - and still use it in tooltip like 'Days since last update'.

In a PBI Embedded scenario (app as a service), users want the ability to show/hide a column in a table.

We need to show count of text fields in the total bar, which again is not supported in Power BI. But somehow managed to create a measure that will show texts in the table and aggregation (count of rows in our case) in the total bar. But this has a limitation that it requires the original column to be in the table visualization, so it is required that we are able to hide it.

We are exploring ways to alter a single table field output to display from cumulative sum to % values basing on text selection.

And, the show and hide column feature is very useful. This feature is available in other tools like SAP WebI.

I needed to sort a table by calculated column but did not want to show the column because it took up space

I think the ability to hide a column in a visual is basic functionality, especially if you want to create dynamic measures to use the hidden column for filtering rows!

We could do this with some conditional creativity in SSRS.

Building a drop down to give the user the ability to "show" the columns they want would be huge!

Needed: hide and show table columns managed by the end user.

* A multinational company with a business unit in each country.
* Every country does maintain the item numbers themselves.
* A worldwide item number format is mapped to the local ones
* Depending on the role the users needs Item and Description:
-> Worldwide only
-> Local only
-> Both

Without this feature we
* either give to much information for some users
* or we have to use bookmarks with a couple of duplicated visuals (Difficult to maintain)
* or we have to create a separated report for every user type (Ugly to maintain)

I totaly agree with Jhinge Pranav. A customer with the requirements above is currently using 200 Qlik licenses and asked us to showcase Power BI. Low brainers like this feature can be a game changer...