How to Edit Relationship in Tableau

Setting up your data sources in Tableau is rarely a one-and-done task. That "noodle" connecting two of your data tables might be linking the wrong fields, causing strange results in your visualization. This guide will walk you through exactly how to edit relationships in Tableau, explaining what each setting does and how to correct common issues.

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

First, What Are Tableau Relationships?

Tableau introduced relationships as its new, more flexible way to combine data from multiple tables. Think of it as a smart join that doesn't permanently merge your tables together. Instead, when you build a visualization, Tableau looks at the relationship you defined and pulls in data from each table only when it's needed for that specific sheet.

This "contextual" approach offers several advantages:

• Flexibility: It prevents data loss that can happen with traditional joins, like dropping records that don't have a match in the other table.
• Performance: Tableau can generate more efficient queries by aggregating data before joining, leading to faster dashboards.
• Simplicity: It simplifies the data source setup, as you just tell Tableau how tables are related, and it handles the rest based on your analysis.

You know you're working with a relationship when you see the flexible orange line - often called the "noodle" - connecting your tables on the Data Source page.

But sometimes, the default relationship Tableau creates isn't quite right. That's when you need to step in and edit it.

Step-by-Step: How to Edit a Relationship in Tableau

Editing a relationship is straightforward once you know where to look. Follow these steps to access and modify the connection between your tables.

1. Navigate to the Data Source Page

First, open your Tableau workbook and go to the Data Source tab, located in the bottom-left corner. This is where you can see all your data tables and the relationships connecting them in the canvas area.

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

2. Open the Edit Relationship Dialog Box

Locate the "noodle" that connects the two tables you want to modify. Click on the noodle itself, and the Edit Relationship dialog box will appear. This window is your control center for defining exactly how these two tables relate to each other.

Inside, you'll see a few key areas to configure:

• The tables being related (e.g., Orders and Customers)
• The fields upon which the relationship is based (e.g., Customer ID)
• Performance Options, which include settings for Cardinality and Referential Integrity.

3. Change the Connecting Fields

The most common edit is changing the fields that link the tables.

Imagine Tableau automatically related your Orders table to your Customers table using a generic "ID" field, but you need them connected by the "Customer Email" field instead. This is simple to fix.

• In the Edit Relationship window, you will see a list of fields for each table.
• Look at the field currently defined under your first table (e.g., Orders). Click the dropdown menu.
• Select the correct field from the list (e.g., "Customer Email").
• Do the same for the second table (e.g., Customers), ensuring you select the corresponding field ("Customer Email").

You can also create a relationship based on multiple fields. Simply click "Add more fields" to create a compound relationship key — for example, relating data on both "User ID" and "Subscription Date". Creating relationships using more fields is a simple and effective method for resolving complex data granularity and aggregation issues you may find in your sources.

4. Set the Cardinality

Cardinality tells Tableau how records in the two tables correspond to each other. Getting this right helps Tableau optimize its queries for better performance. Under the Performance Options tab, you'll find the Cardinality settings.

Here’s what each option means:

• One to One (1:1): Each record in the first table matches exactly one record in the second table. Example: An 'Employees' table and an 'Employee_Contact_Info' table, where 'Employee ID' is a unique key in both.
• One to Many (1:N): One record in the first table can match many records in the second. Example: A 'Customers' table and an 'Orders' table. One customer can place many orders. This is a very common cardinality setting.
• Many to One (N:1): Many records in the first table can match a single record in the second. Example: An 'Orders' table and a 'Customers' table. Many orders can belong to one customer.
• Many to Many (N:N): Many records in one table can match many records in the other. Example: A 'Students' table and a 'Classes' table. One student can take many classes, and one class can have many students.

Tableau tries to detect the cardinality automatically, but its guess might be wrong. If you know, for instance, that one customer can have multiple orders, set the cardinality between your Customers and Orders tables to One to Many.

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

5. Define the Referential Integrity

Just below cardinality, you'll find options for Referential Integrity. This setting tells Tableau whether every record in one table is guaranteed to have a matching record in the other table. Adjusting it can prevent Tableau from dropping necessary records.

Here are your choices:

• All Records Match: This tells Tableau that every record in the table has at least one corresponding match in the other table. This is also known as "inclusion." Selecting this can improve query performance because Tableau won't need to check for non-matching values (an outer join).
• Some Records Match: This is the default and safest setting. It tells Tableau that some records may not have a match. For example, your 'Products' table might contain items that haven't been sold yet, so they wouldn't have a matching record in the 'Sales' table. In this case, 'Sales' will need to have referential integrity set as "Some Records Match."

Common Troubleshooting Scenarios

Sometimes editing relationships involves fixing problems. Here are a few common issues and their solutions.

Scenario 1: The Broken Relationship (Red Exclamation Mark)

If you open your data source and see a red exclamation mark next to a table and a broken noodle, it means the relationship is invalid. This almost always happens because a field used in the relationship was either renamed or removed from the underlying data source.

To fix it:

• Click the noodle to open the Edit Relationship dialog.
• Tableau will highlight the missing or problematic field in red.
• Simply select the new or correct field from the dropdown list to re-establish the link.

Scenario 2: Data Types Don't Match

You can't create or edit a relationship to connect fields of different data types — for example, relating a 'Sales Region' (String) from one table to a 'Region ID' (Number) in another. Tableau won't allow it.

To fix it:

Go back to the Data Source page canvas. For the field causing the issue, click the data type icon (e.g., 'Abc' for String, '#' for Number) and change it to match the type of the field in the other table. Once they match, you'll be able to create the relationship successfully.

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

Scenario 3: Duplicated Data from a Many-to-Many Relationship

Using a many-to-many relationship can sometimes result in overcounted or duplicated rows if not handled correctly. For instance, linking an 'Authors' table directly to a 'Books' table where books can have multiple authors creates this issue.

To fix it:

The best practice is to use an intermediary table, often called a junction or bridge table. This table resolves the many-to-many complexity. For our example, a junction table called 'Book_Authors' would contain two columns: 'Book_ID' and 'Author_ID'.

You would then create two separate one-to-many relationships:

• 'Books' table to 'Book_Authors' table (one book, many entries in the junction table)
• 'Authors' table to 'Book_Authors' table (one author, many entries in the junction table)

This structure accurately models the reality of the data and will prevent incorrect aggregation in your visualizations, especially in financial accounting sheets that are using relationships as lookups for currency conversions and other financial calculations needing precision at the time of aggregation.

Final Thoughts

Editing relationships in Tableau is about fine-tuning how your data tables communicate. By correctly defining the fields, cardinality, and referential integrity, you give Tableau the instructions it needs to build efficient, accurate visualizations and help you avoid common data connection pitfalls.

As powerful as relationships are, sometimes the real challenge is just getting all your data connected and speaking the same language in the first place. Instead of spending time configuring data sources and editing relationships across tools like Tableau or Power BI, we wanted a tool that does the data connection work for you. At Graphed you simply connect your data sources — like Google Analytics, Shopify, Facebook Ads, and Salesforce — and then ask for what you need in plain English. Graphed automatically handles the relationships and data models behind the scenes, instantly building and updating your dashboards so you can get answers instead of wrestling with your setup.