Hide a Column in Power BI: Table Visuals and Models

To hide a column in a Power BI table visual, select the visual and remove that field from its field well; Power BI does not provide a simple per-column Hide switch for a table. To keep a field out of the report-building field list instead, hide it in the semantic model using Hide in report view—this is a different action and does not remove it from existing visuals.

Two different meanings of “hide a column”

The right method depends on what you want readers or report authors to see. A table visual displays fields that have been added to that visual. Removing one field changes the visual’s displayed columns. Hiding a model field changes whether report authors can find and select it in the field list, but it is not a way to conceal that field in a particular visual.

Hide from one table: remove the field from that visual’s field well. The field remains available elsewhere in the report.
Hide from report authors: mark the model column as hidden in report view. It is generally no longer shown as an available field when building reports, but existing visuals can still use it.
Hide values, not the column: use a filter or conditional formatting when the column should remain but some of its contents should not be displayed. These approaches do not actually remove the column.

This distinction matters because “hidden” can sound like a security setting. It is not. Hiding a field from report view is an organizational convenience for the model, not protection for sensitive data.

Remove a column from a table visual

In Power BI Desktop, select the table visual on the report canvas. In the Build visual pane, locate the field in the visual’s field well and remove it using the field’s remove control, or drag it out of the well. Depending on the interface and visual, the well may be labeled Columns or Values. The classic field well for a table commonly uses Values; newer build experiences may present the fields differently.

Open the report page and select the table visual you want to change.
In the Build visual pane, find the column or measure that should no longer appear in that table.
Choose the remove control beside that field, if shown, or drag the field out of the visual’s field well.
Check the visual on the canvas. Resize or reposition the remaining columns if needed, then save the report.

This removes the field from that visual only. It does not delete the source column, alter the data, or remove the field from other visuals. If the same field is used in two separate table visuals, remove it from each one where it should not appear.

In Power BI Service, if you have permission to edit the report, open it in edit mode, select the visual, and make the corresponding change in its visual-building pane. Available editing controls depend on the report and workspace permissions. If you only have reading access, you cannot change the published report; ask its owner to update it or make a copy if that option is available to you.

Hide a field from the report field list

To tidy a model for report authors, hide a column in Power BI Desktop. In Model view or Data view, find the table and right-click the column in the data or model pane, then choose Hide in report view. In some layouts, the same setting is available after selecting the column in the Properties pane. The exact pane arrangement can differ by Desktop version, but the setting is called Hide in report view.

After hiding it, the field is omitted from the normal report field list so authors are less likely to add technical or helper columns to a visual. For example, a customer table might contain a numeric CustomerKey used for relationships and a readable CustomerName intended for reports. Hiding CustomerKey can make the model easier to use without removing the key or breaking its relationship.

Hidden model fields can still matter to the model. Existing report visuals may continue to display a hidden column, and a field used in a measure, relationship, sort order, or other model logic is not automatically deleted. To show it again, find the hidden field in the model and choose the option to unhide it, such as Unhide in report view. Hiding is reversible; deleting a column is a different and potentially disruptive change.

What hiding does—and does not—change

Power BI separates the semantic model from the report visuals built on top of it. A column can exist in the model while being absent from a particular visual, or it can be hidden from the field list while remaining in the model. Neither action should be mistaken for removing the underlying data from the model.

In particular, Hide in report view is not a security boundary. It does not stop a person with suitable model or data access from retrieving information through other means, and it does not replace row-level security, object-level security, or access controls. If a field contains confidential information, use the organization’s approved security and permissions design rather than relying on its hidden status.

Likewise, removing a field from a table visual does not filter its records or change calculations. If a table still shows rows that seem unexpected, the issue may be a filter, relationship, measure, or grouping rather than a column-visibility setting. A table can also show blank values in a field; that is different from hiding the entire column.

Choose the right approach for common goals

Start by deciding whether the intended audience is report readers or report authors. If a reader should not see a particular column in one table, edit that visual. If authors should not routinely select a technical field anywhere in the report, hide it in report view. If nobody should have access to the underlying information, use security controls and review access to the model.

Remove an ID from one displayed table: remove the ID field from that table’s field well. Keep it in the model if relationships or calculations need it.
Keep a helper column out of the authoring list: hide it in report view after confirming that existing visuals and model logic should remain intact.
Show fewer values in a column: apply an appropriate visual or page filter, or change the calculation. The column itself will still be present.
Prevent exposure of sensitive data: configure and test the appropriate model security and permissions; hiding alone is insufficient.

For a reusable semantic model, hide technical fields that are not intended for self-service reporting, but keep names clear and organize related fields into sensible tables or display folders. Avoid hiding every field simply to make the list shorter: authors need to be able to discover the measures and dimensions that the model is designed to provide.

Column headers, widths, and other workarounds

Power BI’s table formatting options can change how a column looks, but formatting is not the same as removing it. You can adjust widths, text, alignment, and other visual properties, yet the table still contains the field. Turning off column headers affects the header row rather than selectively hiding one column, and it may make the table harder to interpret.

Trying to make a column extremely narrow or setting its text color to match the background is usually a fragile workaround. The field can still take up space, reveal values when a user changes formatting, or become visible with a different theme. It can also make the report inaccessible or confusing. If the column should not be part of the displayed table, remove it from that visual instead.

For a requirement such as “show this field only for some users,” a single table’s formatting may not be the right design. Consider separate visuals or report pages with appropriate access controls, or a model security design reviewed for the use case. Conditional formatting is designed to format values based on rules; do not treat it as a dependable way to secure or truly hide data.

Common problems and checks

If a column seems to return after you remove it, first confirm that you selected the intended visual and that the field was removed from its field well. A report page can contain multiple overlapping or similar visuals. Also check whether the field is added to another visual, or whether you are viewing a different saved version of the report.

The field is still in the Fields or Data list: that is expected when you removed it only from a visual. Hide it in report view if the goal is to remove it from the authoring list.
The existing visual still displays a hidden model field: this is expected. Hiding in report view does not remove the field from an already configured visual.
The table changed its sort order: check the visual’s sort setting. A removed field may have been used to sort the table, so choose a suitable remaining field and sort direction.
The table still has an unwanted blank-looking space: inspect the remaining fields and column widths. A blank value, narrow column, or visual layout issue is not necessarily a hidden column.
You cannot edit the report: check whether you have edit permission or ask the report owner. Viewer access does not grant permission to change the published visual.

After changing a model field’s visibility, check important report pages and any dependent reports before publishing. If a field was meant to be hidden only from the authoring list, existing visuals should remain as intended. If you instead delete or rename a field, that can have broader consequences for visuals and calculations, so treat those as separate model changes.

Frequently Asked Questions

Can I hide just one column in a Power BI table visual?
There is no general per-column Hide switch for the table visual. Select the visual and remove that field from its field well. It remains available in the model and can still be used in other visuals.

Does Hide in report view remove a column from existing tables?
No. It hides the field from the normal report-authoring field list, but an existing visual can continue to display it. Remove the field from each visual where it should not appear.

Can I hide a column from viewers but keep it available to report authors?
Removing the field from a visual hides it in that visual for its viewers, while leaving the model field available to authors. For broader restrictions, use the correct security and access controls; model hiding is not security.

Can I hide a column based on a condition?
A table visual does not generally provide a simple conditional switch that removes one entire column for selected rows or users. Filters can change which rows or values appear, but they do not dynamically remove the column itself. Consider separate visuals or a security-aware report design if the requirement is audience-specific.

Will hiding a model column break a relationship?
Hiding a column in report view does not delete it or remove its relationship, so hiding alone should not break that relationship. Deleting the column is different and can affect relationships, measures, and visuals.

How do I show a hidden field again?
In Power BI Desktop, locate the hidden field in Model view or Data view, select or right-click it, and use the option to unhide it in report view. Then it can appear in the report field list again.

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.