How to Duplicate Table in Power BI

Duplicating a table in Power BI is one of those surprisingly useful skills that can save you hours of work and make your data models much cleaner and more efficient. At first, it might seem redundant - why would you need two copies of the same table? This tutorial will show you exactly how to do it and, more importantly, explain the powerful scenarios where duplicating tables is the best move you can make.

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

Why Would You Need to Duplicate a Table?

Before jumping into the "how," let's cover the "why." Duplicating or referencing tables isn't just about creating a backup. It’s a core technique for sophisticated data modeling and analysis. Here are a few common situations where it becomes invaluable:

• Creating Dimension Tables: Often, your raw data is in one large "fact" table that contains everything - sales figures, customer information, product details, and dates. To build a proper data model, you should separate these into distinct dimension tables. For example, you can duplicate a main sales table to create a separate, clean "Products" table or a "Customers" table.
• Building "Role-Playing" Dimensions: A classic example is with dates. A single sales transaction might have an "Order Date," a "Shipping Date," and a "Payment Date." Instead of having one master "Calendar" table and trying to manage multiple, complex relationships to it, you can duplicate your Calendar table three times, renaming them to "Order Date," "Shipping Date," and "Payment Date," each with a clean, single relationship to the sales table.
• Testing Transformations Safely: The Power Query Editor is a powerful tool for cleaning and transforming your data. But what if you want to try out a complex series of steps without messing up your original, working query? Duplicate the table first. This gives you a sandbox where you can experiment freely, knowing your original query remains untouched.
• Creating Summary vs. Detailed Tables: You might need a table showing every single sales transaction for granular analysis, but also a summarized version that shows total sales by month and region for a high-level dashboard. Duplicating or referencing your main sales table and then aggregating it is far more efficient than trying to do everything with DAX measures alone, especially on large datasets.
• Splitting a Single Table into Multiple Tables: Sometimes a single source table contains data that logically belongs in separate tables. For example, an Events table may contain both "Marketing Events" and "Sales Calls." You could duplicate the table twice, then filter one to only show marketing events and the other to only show sales calls, resulting in two clean, distinct tables in your final model.

Two Main Methods for Copying Tables in Power BI

There are two primary ways to create a copy of a table inside the Power Query Editor: Duplicate and Reference. They might sound similar, but they behave very differently and are used for entirely different purposes. Let's break down each one.

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

Method 1: Duplicating a Table

Duplicating creates a completely independent, standalone copy of a query. Think of it as a hard "copy and paste." The new query has its own set of applied steps from the original, but any changes you make to one will not affect the other. This method is perfect for when you want to create a brand new data transformation path based on the same source or for testing things out.

Step-by-Step Guide to Duplicating

1. Open the Power Query Editor: From the main Power BI Desktop screen, click on the Transform data button in the Home ribbon. This will open the Power Query Editor where all the data magic happens.
2. Locate Your Query: On the left side of the Power Query Editor, you'll see a Queries pane listing all the tables (queries) in your report. Find the table you want to copy.
3. Duplicate the Query: Right-click on the query's name to bring up the context menu. Near the top of the menu, select Duplicate.
4. Rename Your New Table: Instantly, a new query will appear at the bottom of the list, usually with the same name as the original followed by (2). It's crucial to rename this immediately for clarity. Right-click the new query, select Rename, and give it a descriptive name (e.g., Sales_Summary or Product_Dimension).

That's it! You now have an exact, independent copy of the original query. If you look at the Applied Steps on the right, you'll see all the transformation steps from the original query have been copied over. You can now add, remove, or modify steps in this new query without having any impact on the original table.

Method 2: Referencing a Table

Referencing a table creates a new, dependent query that points to the output of another query. Instead of copying all the steps, it simply uses the final result of the "parent" query as its starting point. This is an incredibly efficient way to build on work you've already done.

If you make a change to the parent query (e.g., you fix a data type or add a new filtered row), that change will automatically flow down to all the tables that reference it.

Step-by-Step Guide to Referencing

1. Open the Power Query Editor: Just like before, click on Transform data from the Home ribbon.
2. Locate Your Parent Query: In the Queries pane on the left, find the query you want to use as the source.
3. Reference the Query: Right-click on the query's name. From the context menu, select Reference.
4. Rename Your New Table: A new query will appear, and you should rename it to something meaningful. If you click on this new referenced query, you’ll notice something different in the Applied Steps pane - it only has one step: Source. This Source step is simply pointing to the final output of the table you referenced.

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

Duplicate vs. Reference: Which One Should You Use?

This is the most important concept to grasp. Choosing the wrong method can lead to an inefficient data model or unexpected results.

Use Duplicate when:

• You want to try out a completely different set of transformations on the same base data.
• You need an isolated "sandbox" for testing without touching your production queries.
• The new table you are creating needs to branch off from the source very early on and share very few, if any, future transformation steps.

Analogy: Duplicating is like using "Save As" on a Word document. You create a completely separate file (DocumentB.docx) based on an original (DocumentA.docx). Changes you make to Document B have no effect on Document A.

Use Reference when:

• You've already built a "staging" query with all your cleaning steps (e.g., trimming text, changing data types, removing nulls) and you want to use that clean data as a starting point for multiple other tables.
• You want to create a summary table (e.g., monthly sales totals) derived from your fully transformed detail table.
• You are splitting one large, clean table into several smaller, filtered tables. For instance, creating separate tables for each business region from a main All_Sales table.

Analogy: Referencing is like creating a shortcut to an application. The shortcut points to the original program. If the original program gets updated, the shortcut automatically points to the new version. The reference inherits all the work of the parent query, ensuring consistency.

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

Best Practices for Managing Copied Tables

As you start using this technique more frequently, keep these tips in mind to keep your Power BI reports organized and efficient.

• Give Your Tables Descriptive Names: Avoid leaving your tables with default names like Sales (2) or Pageviews (Copy). Rename them immediately to reflect their purpose, such as Sales_ByRegion or Calendar_ShipDate. Clear naming makes your data model far easier for you and a future collaborator to understand.
• Use Query Groups: In the Power Query Editor, you can group related queries together. Right-click in the Queries pane and select "New Group." You could create groups like "Staging Queries," "Dimension Tables," and "Fact Tables" to keep things tidy, especially in complex reports with dozens of queries.
• Add Query Descriptions: For referenced queries with complex logic, use the "Properties" window (right-click the query) to add a description. A simple note like "This table references All Sales and is filtered for the North American region" can save you a ton of time later.
• Be Mindful of Refresh Performance: The Power BI query engine is smart. A technique called query folding often allows it to combine transformation steps and fetch data efficiently. However, when you duplicate a query, you are essentially telling Power BI to execute all the steps for both queries independently. Referencing is often more performance-friendly because the parent query is evaluated once, and its results are cached and fed into any child queries that reference it.

Final Thoughts

Learning how to duplicate and reference tables in Power BI is a fundamental step toward building robust, clean, and scalable data models. Knowing which method to use - an independent 'duplicate' for testing and branching, or a dependent 'reference' for building upon existing work - allows you to structure your data transformations logically and efficiently.

While Power BI transforms how we work with data, spending time in a query editor clicking through steps is still a manual process. This is where we built Graphed to streamline the whole experience. We make it easy to connect all your marketing and sales data sources in one place, and then you can create the charts, reports, and dashboards you need just by describing them in plain English. No more time spent recreating queries - just ask your AI data analyst a question and get the answer back instantly as a live, interactive visualization.