How to Set Primary Key in Power BI

Building relationships between your data tables is the secret to unlocking powerful insights in Power BI, but it all falls apart without one simple thing: a primary key. A missing or incorrect key can lead to miscounted totals, skewed reports, and a data model that just doesn’t work. We'll show you exactly how to identify, verify, and even create a primary key for your tables using Power Query.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Understanding Primary Keys in Power BI

Before we jump into the "how," let's quickly cover the "what." A primary key is a column in a data table where every single value is unique. Think of it like a Social Security Number for a person or a serial number for a product - it’s the one piece of information that uniquely identifies a single row in that table, with no duplicates and no empty values allowed.

On the flip side, you have a foreign key. This is a column in a second table that refers back to the primary key in the first table. For example, your Customers table might have a CustomerID column as its primary key. Your Orders table would then have its own CustomerID column (the foreign key) to link each order back to the specific customer who placed it.

Getting this relationship right is what allows you to create reports that correctly show you how many orders each customer placed or the total revenue per customer.

So, Why Bother with a Primary Key?

Power BI doesn’t technically force you to set a primary key, but failing to have one is the source of countless reporting headaches. Here’s why it’s so important:

• It enables correct relationships: The primary key is the anchor for building one-to-many relationships (e.g., one customer can have many orders), which is the most common and efficient type of relationship in a data model. Without it, you might get many-to-many relationships that slow performance and produce unexpected results.
• It guarantees accurate calculations: When you start writing DAX formulas, Power BI needs well-defined relationships to know how to filter and aggregate your data correctly. A solid key structure ensures your SUM, COUNT, and AVERAGE functions work as expected.
• It prevents data ambiguity: Unique keys eliminate any confusion about which rows belong together. There's no guesswork, which leads to a clean, reliable, and trustworthy data model.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Spotting or Creating a Primary Key in Your Data

Your first step is to investigate your data to see if a suitable key already exists. In the best-case scenario, your database already includes a unique identifier for each table, like product_id, order_id, or customer_email. But you can't just assume it's unique - you need to verify.

Step 1: Use Power Query to Check for Key Quality

The Power Query Editor is your best friend for all data preparation tasks, including key validation. Let's say you think the ProductSKU column in a products table should be your primary key. Here’s how you check it for uniqueness:

1. From Power BI Desktop, click on "Transform data" on the Home ribbon to open the Power Query Editor.
2. Select the table (query) you want to work with from the left-hand pane.
3. Click on the header of the column you suspect is your primary key (e.g., ProductSKU).
4. Navigate to the "View" tab in the top ribbon.
5. In the "Data Preview" section, check the boxes for "Column quality" and "Column distribution".

Power Query will instantly show you metrics above the column header. Here's what they mean:

• Valid: The percentage of rows that contain a value (not empty or error). For a primary key, this must be 100%.
• Error: The percentage of rows with an error. Must be 0%.
• Empty: The percentage of rows that are blank or null. Must be 0%.
• Distinct: The count of all the different values in the column.
• Unique: The count of values that appear only once.

For a perfect primary key, the "Empty" count must be zero and the "Distinct" count must be equal to the total number of rows in your table. If you see that the "Distinct" count is lower than the total row count, it means you have duplicate values to deal with.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Step 2: Handle Duplicates or Missing Keys

When you check your data, you'll usually run into one of three situations. Here’s how to handle each one.

Scenario A: Your Data Has Duplicates

If your ProductSKU column has duplicates, Power Query makes them easy to remove. Simply right-click the column header and select "Remove Duplicates."

But be careful. This action deletes the entire row that contains the duplicate value. Make sure this is what you want to do. If each of those duplicate rows represents a legitimate, separate transaction or entry, removing them will delete your data. In that case, the column isn't a good primary key, and you'll need to create a new one.

Scenario B: Your Data Has No Unique Column (Create an Index Column)

This is a very common problem, especially when working with data from simple spreadsheets or CSV exports. If no single column is unique, you can create your own guaranteed-unique primary key by adding an index column.

An index column simply adds a new column to your table that contains a sequence of numbers, giving each row its own unique ID. Here's the easiest way to do it:

1. With your table open in the Power Query Editor, go to the "Add Column" tab on the ribbon.
2. Click the dropdown arrow next to "Index Column."
3. You can choose for the index to start "From 0," "From 1," or from a "Custom" number. Starting "From 1" is generally the most common and intuitive.

That's it! Power Query will add a new column named "Index" to the end of your table. Each row will have a unique, incrementing number. It’s a good practice to rename this column to something more descriptive, like ProductKey or SalesRecordID, by double-clicking its header.

What if Multiple Columns are Needed for Uniqueness?

Sometimes, no single column is unique on its own, but a combination of columns is. This is called a composite key. For example, in a table listing items in an order, the OrderID will be repeated for every product in that order, and the ProductID will be repeated for every order it's a part of. However, the combination of OrderID and ProductID is unique for each line item.

Power BI works best with a single primary key column, but you can easily create one from a composite key by merging the columns.

Graphed

Still Building Reports Manually?

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

Watch the Demo

How to Create a Composite Key in Power Query

1. In the Power Query Editor, select the columns you want to combine. Hold down the Ctrl key to select multiple columns (e.g., click OrderID, then hold Ctrl and click ProductID).
2. Go to the "Add Column" tab. In the "General" section, click "Merge Columns."
3. A popup window will appear. You can choose a separator to put between the values from the merged columns. A hyphen (-), pipe (|), or colon (:) are good choices.
4. Give your new merged column a name, such as OrderLineID, and click OK.

You now have a new column with values like "1001-A42" and "1001-B57". This single column can now serve as the primary key for your table, because the combination is guaranteed to be unique. Don't forget to use the "Column quality" view to double-check that your new merged column is, in fact, 100% unique!

Final Thoughts

Establishing a proper primary key for each table is a fundamental step in building a reliable and accurate Power BI report. It’s the bedrock of your data model that ensures relationships function correctly and your analysis is trustworthy before you even write your first DAX measure.

Working in Power Query to prep data models is powerful, but often the end goal is just getting fast, clear answers without the tedious setup. At Graphed, we built our tool around this idea. Instead of manually creating index columns, merging keys, and managing data relationships, you connect your data sources - like Shopify, Google Analytics, or Salesforce - and simply ask for what you need in plain English. No need to worry about primary keys, just ask "what was our sales trend last quarter by product category?" and you get an answer instantly. We want to remove the technical hurdles and empower you to have a direct conversation with your data, so you can spend less time cleaning and more time deciding.