How to Link Two Tables in Power BI

Having all your data in Power BI is a great first step, but the real power comes when you connect it all together. If your product information is in one table and your sales figures are in another, you can't build meaningful reports until you link them. This guide will walk you through exactly how to create relationships between tables in Power BI, explaining the 'why' behind each step so you can build flexible, powerful reports.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What Are Relationships in Power BI and Why Do You Need Them?

Think of your data tables like separate spreadsheets. One sheet might have a list of all your products with details like ProductID, ProductName, and ProductCategory. Another sheet has all your sales transactions, including ProductID, QuantitySold, and SaleDate. On their own, they're useful, but limited.

By creating a relationship - linking them using the common ProductID column - you’re telling Power BI how they relate to each other. Suddenly, you can ask bigger questions:

• Which ProductCategory had the highest sales?
• How many units of the ProductName "Premium Widget" did we sell last quarter?
• What is our revenue per customer, broken down by country?

Without linking the tables, answering these cross-table questions is nearly impossible. Creating relationships is the foundation of building a data model, turning isolated sets of data into a unified source of business intelligence.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Fact Tables vs. Dimension Tables: A Quick Primer

To set up relationships correctly, it helps to understand two simple concepts:

• Fact Tables: These tables contain numeric data about events or transactions. A Sales table is a classic example. It records what happened (sales, transactions, clicks, etc.) and is often characterized by having lots of rows.
• Dimension Tables: These tables describe the "who, what, where, and when" of your business. They provide context to your fact tables. Examples include a Products table, a Customers table, or a Calendar table. They are usually shorter and wider than fact tables.

Your goal is to link your fact tables to your dimension tables, which creates a clean, efficient, and powerful model called a "star schema.”

Method 1: Power BI's Auto-Detect Feature

Power BI is smart, and it tries to make your life easier right from the start. When you first load data, it looks for columns in different tables that have the same name and data type. If it finds a match (like ProductID in both your Sales and Products tables), it will often create the relationship automatically.

You can check if this happened by going to the Model view in Power BI, which is the third icon on the left-hand navigation pane. If you see lines connecting your tables, Power BI has already done some of the work for you.

A word of caution: While helpful, auto-detect isn't foolproof. You should always review the automatically created relationships to make sure they are correct. Sometimes, it might create a link based on a column like Date that you didn't intend to link on. It's always a good practice to verify.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 2: Manually Creating Relationships

For full control, creating relationships yourself is the way to go. It’s a straightforward process, and you have two ways to do it in the Model view.

The Drag-and-Drop Approach

This is the most intuitive method for creating a relationship.

1. Navigate to the Model view.
2. Identify the common column that exists in both tables you want to link. This is your "key." For instance, you could use CustomerID to link a Customers table to a Sales table.
3. Click on the key column in the first table (e.g., CustomerID in the Customers table).
4. Hold the mouse button down and drag your cursor over to the corresponding key column in the second table (e.g., CustomerID in the Sales table).
5. Release the mouse button.

Power BI will draw a line between the two tables, and if you hover over it, it will highlight the columns you just linked. Easy as that. You've created a relationship!

Using the 'Manage Relationships' Dialog Box

For more complex models or when dragging feels clunky, the 'Manage Relationships' dialog box gives you a bit more structure.

1. While in any view, find the 'Manage Relationships' button in the Home ribbon tab.
2. A new window will pop up showing all the current relationships in your model. You can also view Power BI's auto-detected relationships here.
3. Click the 'New...' button to create a new one.
4. In the 'Create relationship' dialog:
5. Below the tables, you'll see options for Cardinality and Cross-filter direction. We'll cover those next. For now, you can often leave the defaults.
6. Click OK to create the relationship, then Close to exit the dialog box.

Understanding Relationship Properties: The Important Details

When you create a relationship, Power BI needs you to define a few properties that tell it how the tables relate. Getting this right is critical for your report's accuracy.

Cardinality

Cardinality describes how the data in the two tables corresponds. There are four options, but you'll use one far more than the others.

• One-to-Many (1:*): This is the most common type of relationship. It means that one record in the first table can be associated with many records in the second. For example, one record for "Premium Widget" in your Products table can be related to many sales records in your Sales table. Your "dimension" tables (Products, Customers) will be on the 'one' side, and your "fact" table (Sales) will be on the 'many' side.
• Many-to-One (*:1): This is simply the opposite of one-to-many, depending on which table you list first when creating the relationship.
• One-to-One (1:1): This means one record in the first table is associated with exactly one record in the second. This is less common but could be used, for example, to link an Employees table to an EmployeePayrollDetails table, where each employee has only one payroll record.
• Many-to-Many (:): This type is used when many records in one table can relate to many records in another. A classic example is Students and Classes. A student can take many classes, and a class can have many students. Power BI can handle these, but it's often better practice to create a "bridge" or "junction" table in the middle to simplify the model. Use this one with caution if you are just getting started.

Cross-filter direction

This setting determines how filters flow between your tables.

• Single: This is the default and recommended setting for most models. It means that filters flow "downstream" - from the 'one' side to the 'many' side. For instance, if you filter your report by a product category in the Products table, it will filter the Sales table to show only sales for that category. It's clean, predictable, and reduces ambiguity.
• Both: This allows filters to travel in both directions. In our example, filtering the Sales table could also filter the Products table. While it has its uses in certain complex scenarios, it can sometimes produce unexpected results and make your model logic harder to follow. Stick with 'Single' until you have a specific reason to change it.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Troubleshooting Common Relationship Problems

Sometimes things don't go as planned. Here are some solutions to common issues when linking tables in Power BI.

• The relationship is inactive (a dotted line): Power BI doesn't allow for ambiguity. If there's more than one potential filtering path between two tables, it will make one path "active" and the others "inactive." You can't filter based on an inactive relationship. You can right-click an inactive relationship and make it active, but be sure you understand why the other path existed first.
• My report numbers are wrong or duplicated: This is nearly always a cardinality problem. Double-check that your relationship is correctly set up as a one-to-many and that the 'one' side truly has unique values for the key column. Having duplicate IDs in your dimension table (e.g., two entries for the same ProductID in the Products table) is a common cause of incorrect calculations.
• Power BI says it can't create the relationship due to non-unique values: This error occurs when you try to set up a one-to-many relationship, but the column on the 'one' side contains duplicate values. Go back to the Data view and investigate the column. You'll need to clean it up so that every value is unique before Power BI can create the correct link.

Final Thoughts

Learning to link tables is the moment you unlock the true analytical power of Power BI. By creating clean relationships based on a solid data model, you move from just looking at data to truly understanding what it means and how different parts of your business influence each other. Taking the time to get your one-to-many relationships and single cross-filter directions set up properly will save you headaches later on and make your reports both accurate and insightful.

Connecting data and finding answers is powerful, but navigating tools like Power BI can come with a massive learning curve. Sometimes, you just need a straightforward answer about your marketing or sales without spending your entire day in data models. Here at Graphed , we automate the hard parts. Instead of manually linking tables and building visualizations, you just connect your platforms - like Google Analytics, Shopify, or Salesforce - and ask questions in plain English. We handle the analysis for you, creating live dashboards and reports in seconds so you can get back to growing your business.