Hide a Column in Power BI: Steps and Important Limits

How-to basics · Updated November 22, 2026

To hide a column in Power BI Desktop, find it in the Data or Fields pane, right-click it, and choose Hide in report view. The column stays in the semantic model and can still support relationships, calculations, and existing report content; hiding it only removes it from the fields report authors see when building reports.

What hiding a column means

Power BI separates the data model from the report-building experience. A model can contain columns needed for calculations or data structure even when most report authors should not select them directly. The Hide in report view setting lets you keep such a column in the model while hiding it from the usual field list used to create report visuals.

For example, a sales model might include an integer CustomerKey that links sales rows to customer details. Report authors generally need readable customer names, not the technical key. Hiding CustomerKey keeps the relationship working while making the field list less cluttered. Other good candidates include internal IDs, staging fields, duplicate labels, and helper columns used for sorting.

The setting is a visibility choice, not a deletion. It does not remove the column’s values from the model, change the source data, or guarantee that users cannot access the data. That distinction matters when the column contains confidential or personally identifiable information.

Hide a column in Power BI Desktop

  1. Open the report in Power BI Desktop and locate the column in the Data or Fields pane. In newer versions, the pane may be labeled Data; older versions may call it Fields.
  2. Right-click the column name. If needed, switch to Model view and select the column there instead.
  3. Choose Hide in report view from the context menu. The field should no longer appear among the fields available for building report visuals.
  4. Save the PBIX file. If the report is published, publish the updated version to replace the semantic model and report in the Power BI service.

You can also inspect a column’s properties in Model view. The exact arrangement of panes and commands can vary with Power BI Desktop updates, but the setting is specifically about whether an object is hidden in report view. Hiding a column does not require changing its data type or deleting it from Power Query.

Before hiding a field in a shared model, check whether report authors use it in their work. Existing visuals and model calculations can continue to depend on a hidden field, so hiding it is usually a low-impact model-organization change. However, authors may have difficulty editing a visual that depends on a field they can no longer find.

How to unhide a column

To restore a hidden column to the report-building field list, open Model view and reveal hidden objects if they are not currently displayed. Power BI Desktop provides a Show hidden option in the model-editing interface; its placement can vary by version. Then right-click the hidden column and choose Unhide in report view. Save the file and republish the model if the change needs to reach the service.

Hidden fields can be less obvious than visible ones in the model diagram or pane, so look for the hidden indicator or enable the display of hidden objects before concluding that the column is missing. If a colleague cannot find a field, first confirm that it has not simply been hidden in report view.

What happens to visuals, measures, and relationships

Hiding a field does not automatically remove it from report visuals that already use it. A table visual that displays a hidden column can continue to show that column, and a measure that references it can continue to calculate. The change affects discoverability for report authors, not the model’s underlying calculations.

Relationships also remain in place. A hidden key can still connect a fact table to a dimension table, and a hidden date or sort column can still support model behavior. DAX expressions can continue to refer to hidden columns by their table and column names. Keep these dependencies in mind before renaming or deleting a field: those are different changes and can break visuals, relationships, or calculations.

Hiding a source column used by a hierarchy or another model feature does not mean that the related model object has been deleted. Check the hierarchy and any existing visuals after making changes, especially if report authors need to edit them. A useful practice is to hide implementation details while leaving user-facing fields, measures, and useful hierarchies visible.

Hide a field globally or remove it from one visual?

Use Hide in report view when the field should generally not be offered to report authors anywhere in the model. If you only want to remove a field from one chart, table, or other visual, select that visual and remove the field from its build or data well instead. The field remains available for other visuals and authors.

For instance, a report page may show total sales by month without showing the underlying transaction ID. Remove the transaction ID from that page’s visual if it was added by mistake. Hide the ID in the model only if it is a technical field that report authors should not normally use across the report. This distinction avoids making a model-wide change to solve a one-visual formatting or design issue.

Another separate action is removing a column from the model. In Power Query Editor, removing a column and applying the query changes means the column is no longer loaded into the model. That can reduce model size, but it may break relationships or DAX expressions that depend on the column. Choose based on the goal: simplify the field list, adjust one visual, or actually exclude data from the model.

Choose good candidates for hiding

Think about how report authors are expected to use the model, not just how a field looks in a table. A column that is confusing or purely technical is often a good candidate. A column needed for analysis, filtering, or drill-down may be better left visible, even if its name needs improvement.

  • Technical keys: Hide surrogate IDs and join keys when authors should use descriptive names instead.
  • Helper columns: Hide fields used only to sort a visible label or support a model calculation, provided authors do not need them directly.
  • Duplicate or internal fields: Hide confusing copies or administrative fields that are not intended for report design.
  • Useful business fields: Keep customer segment, product category, date, and other fields visible when they are valid ways to explore the data.

Clear names and descriptions can be better than hiding a field that users genuinely need. For example, a column named CustGrpCd may be more useful after renaming it to Customer Group Code. A well-organized model typically combines sensible table names, descriptive fields, measures, and selective hiding rather than concealing large sections of the model.

Hiding is not data security

A hidden column remains part of the semantic model. Hiding it does not encrypt the values, remove them from the model, or grant and revoke access. Depending on permissions and available features, users with access to the model may be able to inspect data or query the model through other tools. Data export and Analyze in Excel behavior also depend on the report, model, and user permissions; do not treat a hidden field as protected from access.

If a column must not be accessible to particular users, use an appropriate security control rather than Hide in report view. Row-level security (RLS) restricts which rows users can see. Object-level security (OLS), where supported and configured for the model, can restrict access to specified tables or columns. These controls require deliberate configuration and testing with the intended user roles. Follow your organization’s security requirements for sensitive data.

Likewise, if the goal is to reduce model size or prevent a column from being loaded at all, remove it from the Power Query load or change the upstream data process as appropriate. Verify that no relationships, measures, or report visuals depend on it before doing so.

Common problems and checks

  • The field is still in an existing visual: That is expected. Hiding a column does not automatically remove it from visuals already built with it.
  • The field seems to have vanished from the model: Show hidden objects in Model view and check the column’s hidden status before assuming it was deleted.
  • A report author cannot find a needed field: Unhide it, or provide a clearly named alternative. Remember that changing the model may require republishing.
  • The data still appears to be accessible: Hiding is not a security feature. Review model permissions and configure appropriate security controls.
  • A measure or relationship stopped working: Hiding alone should not remove the field. Check whether it was also renamed, deleted, or removed in Power Query.

When publishing a change, remember that the Desktop file and the published semantic model are separate until the updated PBIX is published. If a report is connected to a shared semantic model, make the change in the model’s source file or use the appropriate model-editing workflow. A report connected to a shared model may not let its author change the model structure directly.

Frequently Asked Questions

Can I hide a column in Power BI without deleting it?

Yes. Choose Hide in report view from the column’s context menu. The column remains in the semantic model and can continue to support relationships, calculations, and existing visuals.

Can users still see a hidden column’s data?

Potentially. Hiding only removes the field from the normal report-authoring field list; it is not a security boundary. Use permissions and supported security features such as RLS or OLS when access must be restricted.

Will hiding a column break a measure or relationship?

Hiding by itself should not break either. The model can continue using the column. Deleting, renaming, or removing it from the model is different and can break dependencies.

How do I hide a column in only one visual?

Select the visual and remove the field from its build or data well. Do not hide the column in the model if it should remain available to other visuals or report authors.

Can I hide a column in Power BI Service?

Model-editing options in the service depend on the model and available web-editing features. The common, dependable workflow is to change the model in Power BI Desktop, save the PBIX, and publish the updated version. If the report uses a shared semantic model, edit the model through its authorized source workflow.

Related

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.