How to Hide Queries in Power BI

Your Power BI report looks incredible. The visuals are clean, the DAX measures are firing perfectly, and the insights are compelling. However, when a colleague opens the Power Query Editor to see how you built it, they're met with a tangled mess of queries, temporary tables, and helper columns. Cleaning up this backend for collaboration is just as important as perfecting the front-end dashboard. This guide will walk you through how to hide and organize your queries in Power BI to make your reports cleaner, faster, and much easier for others (and your future self) to understand.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

So, Why Bother Hiding Queries?

You might think, "It works, so who cares what the back end looks like?" A clean Power Query pane isn't just about aesthetics, it’s about creating professional, maintainable, and user-friendly reports. Consider it the difference between a mechanic who leaves tools scattered everywhere and one who neatly organizes their workshop.

Here are the core reasons to tidy up your queries:

• Reduce Visual Clutter: If you have dozens of queries, many of which are just intermediate steps (like merging files, filtering, or creating reference tables), it can be overwhelming for someone to find the final, important tables that actually feed the report.
• Improve the User Experience: When you hand off a report, you want your teammates to focus on the key output tables. Hiding the "helper" queries guides them directly to what's important, reducing confusion and saving them time.
• Protect Your Work: Intermediate queries are often delicate. Hiding them reduces the risk that someone will accidentally modify or delete a critical staging step that could break your entire data model.
• Signal Importance: An organized query list clearly signals which tables are data sources, which are staging transformations, and which are shiny new output tables ready for analysis.

The Primary Method: Disable Report Load

The main way to "hide" a query in Power BI is to prevent it from loading into your Data Model. This is a crucial concept. The query still exists in the Power Query Editor, it still refreshes its data, and other queries can still reference it. It just won’t appear as a table in the Report View or Data View in your final Power BI file.

This is the perfect technique for any "helper" queries - the ones used for transformations, merging, appending, or calculations, but which aren't the final table you want to use in your visuals.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step-by-Step: How to Disable Load

Let's walk through a common scenario. Imagine you have two separate CSV files: one for "North Region Sales" and one for "South Region Sales." Your goal is to combine them into one master table called "Total Sales" and only show that final table in your report.

1. Import Your Data: Start by importing both CSV files. You'll now have two queries in your Power Query Editor: North_Region_Sales and South_Region_Sales.
2. Create the Final Query: Create a new query that appends the two tables. You can do this by selecting one table, clicking "Append Queries" on the Home tab, and choosing the second table. Let’s rename this combined query to Total_Sales. You now have three queries in total.
3. Disable Load on the Helper Queries: In the Queries pane on the left, right-click on the North_Region_Sales query. In the context menu that appears, you will see a checkmark next to Enable Load. Click it to uncheck it. The query name will immediately become italicized.
4. Repeat the Process: Do the same for the South_Region_Sales query. Right-click and uncheck Enable Load.
5. Close & Apply: Click "Close & Apply" in the top-left corner.

When you return to the main Power BI window, look at your "Data" pane on the right. You will only see one table: Total_Sales. The two source queries, North_Region_Sales and South_Region_Sales, are not there. They did their job in the background and gracefully exited, leaving a clean field for analysis.

When should you use this method?

• Merging Tables: Just like our example, when combining multiple data sources into a final, unified table.
• Staging Transformations: If you have one query to pull raw data and a second query that references the first one to perform a series of complex cleaning steps. Your final visuals only need the cleaned-up version, so you can hide the raw data query.
• Reference Tables: For creating tables that are used by other queries but not directly in visuals, such as a list of dates, a helper parameter table, or a de-duplicated list of customers for merging purposes.

Keep in mind that Power BI is smart. If one query references another, it will often warn you if you try to disable the load on the source query without being intentional. This helps prevent you from accidentally breaking your refresh logic.

The Organizational Method: Using Query Groups

Sometimes, you don't necessarily want to hide queries from the data model, but you need to wrangle the chaos in the Power Query Editor itself. If your report connects to ten different data sources and has thirty transformation steps, your query list can quickly become a mess. This is where Groups come in handy.

Groups act like folders, allowing you to organize your queries into collapsible sections. It’s an organizational tool that drastically improves readability.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step-by-Step: How to Use Query Groups

Let’s continue with our example, but expand it a bit. Pretend we also have a query for "Product_List" and another for "Employee_Directory."

1. Select Queries to Group: Open your Power Query Editor. In the Queries pane, select the queries you want to group together. Let's start with our original sources. Hold down the Ctrl key and click on North_Region_Sales and South_Region_Sales.
2. Create a Group: Right-click on one of the selected queries. In the menu, navigate to Move To Group > New Group...
3. Name Your Group: A small dialog box will appear. Give your group a descriptive name, like "01 - Data Sources". Using numbers in front of the name helps control the order in which groups appear. Click "OK".
4. Organize Remaining Queries: Now, let's create a group for our cleaned-up output. Right-click the Total_Sales query, and create a new group called "02 - Final Output Tables". You can right-click any remaining queries (like Product_List and Employee_Directory) and move them into an existing group.

Once you’ve done this, your query pane will look incredibly neat. You can collapse the "01 - Data Sources" group to hide those details and just focus on your output tables. It's an excellent way to guide anyone looking at your work through your data transformation process logically.

Best Practice: Combine Both Techniques for Zen-Like Cleanliness

For truly professional and scalable reports, the best approach is to combine both methods. You organize queries into logical groups and disable the load on any helper, staging, or source queries that aren’t needed in the final report.

A typical, clean workflow looks like this:

1. Create a "Staging" or "Sources" Group: Pull in all your raw data sources and immediately move them into a group named something like "Staging Area" or "Raw Data".
2. Build Your Transformations: Create new queries that reference the raw data. Perform all your cleaning, merging, and appending in these new queries. Let's say you placed these in a "Transformations" group.
3. Disable Load on Everything in Staging: Once you have your final output tables, right-click the entire "Staging" and "Transformations" groups and disable the loading of every query within them. Only your final, beautiful, analysis-ready tables should have "Enable Load" checked.

Now, you have the best of both worlds: a highly organized Power Query Editor and a lightweight, clean Data Model containing only the tables that matter.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Wait, What About "Hide in Report View"?

You might be familiar with another "hiding" feature directly in the main Power BI window. If you're in the Report or Data view, you can right-click any table or column in the Data pane and select "Hide."

So, what’s the difference?

• Disabling Load (Power Query): This removes the table from the data model entirely. The data is not loaded into memory. It cannot be used in visuals, and its columns are not visible anywhere outside the Power Query Editor.
• Hiding in Report View: This simply conceals the table or column from the Report View. The data is still loaded into your model, taking up memory and being fully available for DAX measures and relationships. It is just invisible to the report creator, hiding it from the field list to avoid building charts from unnecessary items like key IDs used only for table relationships.

Use "Disable Load" for your helper queries during the transformation phase. Use "Hide in Report View" for things like ID columns used to join tables or tables full of measures that end users shouldn't interact with directly.

Final Thoughts

Cleaning up your Power BI reports by hiding and grouping queries is more than just a nice-to-have skill. It's a fundamental practice that separates an amateur from a professional. By disabling unnecessary loads and organizing transformation steps into logical groups, you create reports that are easier to manage, faster to load, and infinitely more approachable for collaboration.

Mastering these nuances in Power BI is a valuable skill, but it also highlights the learning curve involved in traditional BI. The time spent organizing queries, optimizing data models, and perfecting each setting is precisely the friction we wanted to eliminate when we built our platform. With Graphed, we connect directly to your marketing and sales data sources like Google Analytics, Shopify, and Salesforce, and automate the entire transformation and visualization process. Instead of manually wrangling queries, you just ask a question like "Create a dashboard comparing our Facebook Ads spend to our Shopify revenue by campaign," and the dashboard is instantly built for you using live, real-time data.