Hide a Column in a Power BI Table: Options Explained

Yes, but the right method depends on what you mean by “hide.” To remove a column from one table visual, select the visual and remove that field from its field well; to keep it out of report authors’ field lists, hide the column in the model. Those approaches have different effects, and neither protects sensitive data.

What “hide a column” can mean

Power BI has both data-model tables and report visuals. A model table is the collection of fields loaded into or created in the semantic model. A table visual is a particular display of selected fields on a report page. Because these are different layers, hiding a model column is not the same as removing a column from a visual.

For a single table visual, the usual approach is to remove the field from that visual. The visual then no longer displays the column, but the column remains in the model and can still be used elsewhere. If you want report authors not to see a field when they browse the model, use Hide in report view. That makes the field less prominent in authoring without deleting it.

There is not a general-purpose switch that makes a table visual retain a column’s data and behavior while simply making that column invisible. If a visual needs a field for a particular calculation or interaction but readers should not see it as a displayed column, consider a different design, such as a measure, tooltip, or separate visual. The best option depends on what the field is doing.

Remove a column from one table visual

In Power BI Desktop, select the table visual on the report canvas. In the Build visual pane, locate the field well containing the visual’s columns. Depending on the current pane layout, this may be labeled Columns or appear as a list of fields used to build the visual. Remove the field you do not want displayed, commonly by selecting its remove control or opening its menu and choosing Remove field.

Select the table visual, not the column in the data model.
Find the unwanted field in the visual’s Build visual field well.
Remove that field from the visual.
Check the table’s remaining columns, totals, sorting, and formatting on the report canvas.

This change affects the selected visual only. If the same field appears in another table or chart, that other visual is unchanged. Removing a field can also affect how the table is sorted or summarized, so inspect the result rather than assuming the layout will be identical apart from one column. To restore it, add the field back from the model’s field list.

For example, a sales table might show Customer, Order Date, Product, Units, and Revenue. Removing Order Date from that visual gives readers a simpler product-and-revenue view, while the date column remains available for a separate timeline or another visual. It does not delete dates from the underlying data.

Hide a field from the report field list

Use Hide in report view when the goal is to simplify the model for report authors—for example, by hiding an internal key column that users should not select directly. In Power BI Desktop, find the column in the Data or Model view, right-click it, and choose Hide in report view. The exact pane arrangement can vary with the Desktop interface, but the command is available from the field’s context menu.

The field is then hidden from the normal report field list, making it less likely that an author will add it to a new visual. The column remains in the semantic model, however. Hiding it is not deletion, and it is not a permission boundary. Existing model logic can still depend on it, and a hidden field may still be relevant to existing visuals or calculations.

This feature is useful for organizing a model. Common candidates include technical IDs, duplicate fields, helper columns, and columns intended only for relationships or model calculations. Before hiding one, check whether report authors need it for legitimate analysis. A descriptive label or a well-named measure may be a better user-facing choice than hiding a field people need.

What happens to sorting, calculations, and relationships?

Removing a field from a visual changes that visual’s field selection. It does not, by itself, remove the column from the model or break a relationship. Hiding a column in report view likewise changes its visibility to report authors rather than removing its stored values. This distinction is important when a column is used behind the scenes.

A column can be useful even when it should not appear in a table. For instance, a product code may provide a unique key or control a Sort by column setting for a product name. A date column might support a measure or a relationship even if a particular visual displays only month and sales. Avoid deleting or replacing such fields simply because readers should not see them in one display.

After removing a displayed field, check whether the visual’s sort order changes. A table may have been sorted by the removed column, and the remaining order may not match what readers expect. Also review totals and conditional formatting: those settings may have been applied to the removed field, so they will no longer be visible there. Model measures and relationships are separate from the visual’s displayed columns, but the report’s behavior should still be checked after editing.

Can you hide the column but keep its data in the visual?

Usually, not as a simple hide-and-retain operation in a standard table visual. If you remove a field from the visual, it is no longer one of the visual’s displayed fields. If you leave the field in the visual, its column is generally part of the table’s display. Hiding the underlying model field from report view does not serve as a reliable way to make an already displayed visual column disappear.

There are workarounds for particular requirements, but they do not all behave like a hidden column. You might use a measure to calculate a result without exposing an intermediate field, put supporting information in a tooltip, or use separate visuals for different audience needs. A field parameter can let readers choose which fields appear, but it is a choice mechanism, not a security feature, and requires model and report setup.

Making a column extremely narrow or changing its text color to match the background is not a sound substitute. Readers may still see a header, a resize boundary, or values under a different theme, and accessibility suffers. Prefer a clear visual design over formatting tricks that make information difficult to find or interpret.

Hide, remove, delete, or secure: the differences

Remove from a visual: the field stops appearing in that particular visual, but remains in the model and may be used elsewhere.
Hide in report view: the field is omitted from the normal authoring field list, but remains part of the model.
Delete from the model: the column is removed from the model, which can break visuals, measures, relationships, or other dependencies.
Restrict access: security controls determine what a user can access; hiding a field is not a substitute for those controls.

The distinction matters most when a field contains confidential or regulated information. A hidden column is not encrypted, erased, or made inaccessible to someone with ways to query or inspect the model. If a user must not access the data, design and test appropriate model or data-source security, such as row-level security where it applies, and do not rely on visual formatting or Hide in report view.

Choose the method that fits the report

Start by identifying who should not see the field and where it should be unavailable. If the field is unnecessary in one table but useful elsewhere, remove it from that visual. If it is confusing or technical for report authors but still needed in the model, hide it in report view. If readers need to switch between different sets of visible fields, consider a field parameter or purpose-built report pages. If access to the underlying information must be restricted, address security rather than appearance.

Consider the report’s audience, too. In a report maintained by a small team of model authors, visible technical fields may be manageable. In a model designed for self-service reporting, hiding implementation details can make the field list much easier to use. A clean model often groups fields, uses descriptive names, and exposes useful measures, rather than relying on visual-level fixes alone.

For a presentation where different audiences need different levels of detail, separate pages or visuals can be clearer than trying to conceal a column. For example, an executive page may show aggregated revenue while an operational page includes order-level details. If access must differ by user, configure appropriate security and test it as the intended user; hiding a page element alone does not ensure that the data is inaccessible.

Common problems and checks

If a field still appears after you remove it, first confirm that you selected the correct visual and removed the field from that visual’s field well. A report page can contain multiple table visuals, and another visual may still use the same column. If it appears in the Fields or Data list, that is a separate issue: remove it from a visual to change that visual, or use Hide in report view to change its authoring visibility.

If the field disappears from the model field list but an existing report still relies on it, do not assume the model has lost the data. Hidden and deleted are different states. Conversely, if you delete a field to try to hide it, Power BI may report broken dependencies or visuals. Check the model and any dependent reports before deleting columns.

Finally, test the report in the view your audience uses. Verify that the table has the intended columns, that sorting and totals make sense, and that filters and tooltips still work. If confidentiality is the concern, test permissions separately; a tidy visual is not proof that the underlying data is protected.

Frequently Asked Questions

Can I hide a column in just one Power BI table visual?
Yes. Select that visual and remove the field from its Build visual field well. The change applies to that visual, not to every visual or to the model column itself.

Does Hide in report view remove the column from the data model?
No. It hides the field from the normal report-authoring field list but leaves it in the model. It is different from deleting the column.

Can I hide a column from report viewers but keep it available to report authors?
Removing it from a visual keeps it out of that visual for viewers while leaving the model field available to authors. If it is present on another visual or page, it can still be displayed there.

Does hiding a column protect sensitive information?
No. Hiding a field or removing it from a visual changes presentation or authoring visibility; it does not secure the data. Use appropriate data and model security for access restrictions.

Can I hide a column header but still use the column in the table?
A standard table visual does not offer a general-purpose invisible-column setting that preserves the field as a displayed table column. Consider a measure, tooltip, field parameter, or separate visual for the underlying need.

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.