Can You Hide a Column in a Power BI Table Visual?

Not with a dedicated hide-column switch in a Power BI table visual. To make a column disappear, remove its field from that visual; if you need viewers to choose columns or need to restrict access to data, use a different approach designed for that purpose.

What “hide a column” means in Power BI

People often use “hide” to mean several different things. In a table visual, they may want a field gone from the displayed table but still available elsewhere in the report. They might instead want to remove a field from the authoring field list, conceal its values from viewers, or prevent certain users from accessing the data. Those are separate tasks, and the right solution depends on which one you mean.

For an ordinary table, the straightforward display change is to remove the field from that visual. This does not delete the column from the semantic model or affect other visuals that use it. Power BI does not provide a standard table-formatting option that keeps the field in the visual’s field list but makes its entire column genuinely invisible to readers.

Remove a field from one table visual

In Power BI Desktop, select the table visual, then find its field well in the Build a visual pane. The table’s well is commonly labelled Columns; some interface versions or older layouts may use a different label, such as Values. Remove the field you do not want in the table by using the field’s remove control or context menu, or by dragging it out of the well.

Select the table on the report canvas.
In the visual’s field well, locate the column to remove.
Use the remove option for that field, or drag it out of the well.
Check the table and any dependent totals or formatting to confirm the result is what you intended.

This removes the field only from the selected visual. The underlying model column remains available to other report visuals and calculations, provided it is otherwise available to the report author. If the table is used on several report pages, you may need to remove the field from each visual separately. Removing it from one table does not automatically update copies elsewhere.

Hide a model column from the report field list

Power BI also has a model-level command called Hide in report view. In Model view, select or right-click a column and choose that command. The column is then omitted from the field list used for report authoring, which can make a model easier to navigate when it contains technical keys, helper fields, or columns intended only for calculations.

This is not the same as hiding a column in one table visual. It is a model usability setting, not a data-security control. It does not remove the column from the semantic model, and it does not erase values. A visual that already refers to the field may continue to use it; hiding a model field is not a reliable way to make an existing table stop displaying it. Remove the field from the visual itself when the goal is to change what that visual shows.

For example, a model may contain an internal CustomerID used to connect tables. Hiding that field from report view can discourage authors from adding it accidentally, while a customer-facing table can show Customer Name and Sales instead. The relationship and the underlying identifier remain part of the model.

Why formatting is not the same as hiding

Some workarounds make a column less noticeable: shrinking its width, matching its text colour to the background, or changing its formatting. These do not truly remove the field. The header, blank space, hover behaviour, export output, or accessibility experience may still reveal that something is there, and a report change can make the concealed values visible again.

Formatting is appropriate when the goal is visual emphasis—for example, dimming a secondary value or reducing the width of a long identifier that readers rarely need. It is a poor choice when the values are confidential or must not be available. Nor does reducing a column’s width to nearly zero constitute dependable hiding: users may be able to resize it, and the column can still be included when data is exported.

If a column should not be part of the reader’s view at all, remove it from the visual. If it must be unavailable to particular people, address access in the semantic model rather than relying on appearance.

Let viewers choose which columns appear

If readers need different sets of fields, a field parameter can provide a controlled way to change what a visual displays. In Power BI Desktop, create one from Modeling > New parameter > Fields, select the fields to offer, and use the generated parameter in the table and its associated slicer. A viewer can then select a field or set of fields from the choices you provide. The exact interaction depends on the parameter and slicer configuration.

This is useful for reports where different audiences want to compare different attributes—for example, a product table in which a reader can choose to show brand, category, or supplier. It avoids maintaining a separate fixed table for every field combination. However, a field parameter is a selection mechanism, not an access-control feature: it should not be used to protect sensitive model data from someone who has permission to query that data.

Another option is to create separate visuals with different columns and use bookmarks and buttons to switch between views. This gives the author precise control over each layout, but the report requires more maintenance. If a measure, title, or style changes, you may need to update each version. For a small number of clearly distinct layouts, that trade-off can be worthwhile.

Security: hiding is not restricting access

A column that is absent from a table visual may still be available through another visual, another report, or a query against the semantic model, depending on the user’s permissions. Hiding a field from report view and disguising it with formatting are also not security measures. Do not put sensitive information in a report on the assumption that viewers cannot get it because they cannot see it on one page.

Power BI security features address different requirements. Row-level security (RLS) filters which rows a user can access; it does not, by itself, hide selected columns. Object-level security (OLS) can restrict access to model objects such as tables or columns for users assigned to the appropriate roles. OLS configuration and availability depend on the model and authoring tools in use, so confirm the setup and test it with the intended user roles before publishing.

For confidential data, define permissions and model security deliberately, then test what a viewer can see and query. Keep only necessary data in a shared model, assign report and model access carefully, and follow your organization’s governance requirements. A report’s visual layout controls presentation; permissions and semantic-model security control access.

Tables, matrices, exports, and accessibility

A table visual presents fields as columns, while a matrix organizes fields into row and column groups and can show expandable hierarchies. Collapsing a matrix hierarchy changes which grouped details are displayed; it is not the same as hiding a model column or securing data. If a field is not needed in the table’s output, remove it from the relevant visual’s field well.

Also consider what happens beyond the canvas. A field removed from a visual will not be part of that visual’s displayed table, but report users may have other ways to access model data if permissions allow. Export options and their contents depend on the report, visual, and Power BI settings. If your requirement is that a value never be available to a certain audience, test the relevant export and access paths rather than judging only by the on-screen appearance.

Accessibility is another reason to avoid invisible-text tricks. A value that has been visually camouflaged may remain confusing to keyboard, screen-reader, or high-contrast users. Use the visual’s actual field selection to control its contents, and reserve formatting for information that should remain available but look less prominent.

Common issues and how to resolve them

The field still appears in another table. Removing a column from one visual does not remove it from other visuals. Select each affected visual and remove the field there, or use a field parameter or bookmarks if readers need alternate views.
The field is missing from the authoring list. It may be hidden in report view. In Model view, locate the column and change its Hide in report view setting if authors should be able to select it.
A hidden-looking column appears in an export. A narrow width or matching text colour only changes presentation. Remove the field from the visual or review model permissions and security if the concern is access.
A total or calculation changes after removal. Check whether the field was only displayed or also used as a visual grouping, filter, or sort field. Removing a grouping field can change the granularity of the table and therefore the values shown.
The field well has a different name. Power BI’s editing interface can vary by version and interaction mode. Look for the selected visual’s field assignment area in the Build a visual pane; the table’s fields may be listed under Columns or a legacy label.

Frequently Asked Questions

Can I hide a column in Power BI without removing it from the visual?
There is no standard hide toggle for an entire table column that leaves it in the visual but makes it genuinely invisible. Remove the field from the visual, or use a field parameter or alternate visuals if viewers need to switch between layouts.

Does Hide in report view remove a column from an existing table?
It is intended to hide the field from report authors’ field list, not to alter a visual’s displayed contents or protect the data. Remove the field from the visual if you need it gone from that table.

Can viewers show a hidden column themselves?
If the field was removed from a fixed visual, viewers generally cannot add it back through that visual’s field well in a published report. But the field may be available elsewhere if their permissions allow it. A field parameter can deliberately let viewers choose among fields you offer.

Can I hide a column based on a slicer selection?
A regular table does not have a universal conditional hide-column switch. Field parameters can let a slicer control which fields appear, while bookmarks can switch between prebuilt visual layouts. Choose based on how flexible the selection needs to be.

Does hiding a column protect confidential values?
No. Removing a field from a visual, hiding it in report view, or making its text blend into the background does not secure the underlying data. Use appropriate semantic-model permissions and, where suitable, object-level security, then test access as the intended audience.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.