Data relationships model in Tableau - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a data relationship model in Tableau?

A data relationship model in Tableau defines how different tables connect and relate to each other without merging them into one table. It helps Tableau understand how to combine data when creating visualizations.

intermediate

What is the difference between a relationship and a join in Tableau?

A relationship keeps tables separate and combines data only when needed, preserving their original structure. A join merges tables into one before analysis, which can cause duplication or data loss.

beginner

What types of cardinality can you set in Tableau relationships?

Tableau allows setting cardinality as one-to-one, one-to-many, or many-to-one to describe how rows in one table relate to rows in another.

intermediate

Why is using relationships preferred over joins in Tableau for large datasets?

Relationships improve performance by combining data only when needed and avoid data duplication, making analysis faster and more accurate on large datasets.

intermediate

How does Tableau handle filters with data relationships?

Filters apply to related tables dynamically, so Tableau only pulls relevant data from each table based on the filter, improving speed and accuracy.

What does a data relationship in Tableau do?

A Deletes duplicate rows automatically

B Joins tables into one big table immediately

C Connects tables without merging them until needed

D Creates a new table with combined columns

Relationships connect tables logically but keep them separate until Tableau needs to combine data for analysis.

Which cardinality type means one row in Table A matches many rows in Table B?

A One-to-many

B Many-to-one

C Many-to-many

D One-to-one

One-to-many means one row in the first table relates to multiple rows in the second table.

Why might you avoid using joins on large datasets in Tableau?

A Joins always improve performance

B Joins can cause data duplication and slow down analysis

C Joins remove important columns automatically

D Joins do not allow filtering

Joins merge tables upfront, which can duplicate data and slow down performance on big datasets.

How does Tableau apply filters when using data relationships?

A Filters apply only to the first table

B Filters are ignored with relationships

C Filters create new tables

D Filters apply dynamically to all related tables

Filters dynamically limit data from all related tables, improving efficiency.

Which is NOT a benefit of using data relationships in Tableau?

A Automatically cleans data errors

B Better performance on large data

C Preserves original table structures

D Flexible combining of data when needed

Data relationships do not clean data errors automatically; they manage how tables connect.

Explain what a data relationship model is in Tableau and why it is useful.

Think about how Tableau connects tables without merging them upfront.

Describe the difference between a relationship and a join in Tableau with an example.

Consider how data is combined and when.

Practice

1. What is the main purpose of using data relationships in Tableau?

easy

A. To delete unrelated tables automatically

B. To permanently combine tables into one

C. To create duplicate copies of data

D. To connect tables without merging them immediately

Solution

1. Step 1: Understand what data relationships do

   Data relationships link tables by matching key fields but keep tables separate until analysis.

2. Step 2: Compare with other options

   Options A, B, and C describe deleting, permanently combining, or duplicating, which are not the purpose of relationships.

3. Final Answer:

   To connect tables without merging them immediately -> Option D

4. Quick Check:

   Relationships connect tables without merging [OK]

Hint: Relationships link tables without merging data [OK]

Common Mistakes:

• Confusing relationships with joins
• Thinking relationships merge tables immediately
• Assuming relationships duplicate data

2. Which of the following is the correct way to create a relationship between two tables in Tableau?

easy

A. Write a SQL JOIN statement manually

B. Drag a field from one table to the matching field in another table

C. Copy data from one table and paste into another

D. Use the Data Interpreter to merge tables

Solution

1. Step 1: Identify how Tableau creates relationships

   Tableau allows creating relationships by dragging a key field from one table to the matching field in another.

2. Step 2: Eliminate incorrect methods

   Options A, C, and D describe manual SQL, copying data, or using Data Interpreter, which are not how relationships are created.

3. Final Answer:

   Drag a field from one table to the matching field in another table -> Option B

4. Quick Check:

   Drag matching fields to create relationships [OK]

Hint: Drag matching keys between tables to create relationships [OK]

Common Mistakes:

• Trying to write SQL JOINs instead of using drag-and-drop
• Copy-pasting data instead of linking tables
• Confusing Data Interpreter with relationships

3. Given two tables: Orders with fields OrderID, CustomerID and Customers with fields CustomerID, CustomerName, what will happen if you create a relationship on CustomerID and then create a view showing CustomerName and count of OrderID?

medium

A. The view shows each customer with the number of their orders

B. The view shows all orders without customer names

C. The view shows customer names but no order counts

D. The view causes an error due to missing join

Solution

1. Step 1: Understand relationship on CustomerID

   Relationship links Orders and Customers on CustomerID, allowing data from both tables to combine logically.

2. Step 2: Analyze the view with CustomerName and count(OrderID)

   Tableau aggregates orders per customer, showing customer names with their order counts.

3. Final Answer:

   The view shows each customer with the number of their orders -> Option A

4. Quick Check:

   Relationship on CustomerID aggregates orders by customer [OK]

Hint: Relationship on key fields enables combined aggregation [OK]

Common Mistakes:

• Expecting no aggregation without explicit join
• Thinking relationship causes errors
• Assuming customer names won't appear without join

4. You created a relationship between two tables on ProductID, but your view shows incorrect totals. What is the most likely cause?

medium

A. The relationship was created on non-matching fields

B. The tables are physically merged instead of related

C. You forgot to refresh the data source

D. The relationship uses fields with different data types

Solution

1. Step 1: Check the fields used in the relationship

   If the relationship is created on fields that do not match correctly, the data will not combine as expected, causing wrong totals.

2. Step 2: Evaluate other options

   Data type mismatch usually prevents relationship creation; physical merge creates a single table instead of relating; refreshing rarely fixes relationship logic errors.

3. Final Answer:

   The relationship was created on non-matching fields -> Option A

4. Quick Check:

   Incorrect totals often mean wrong relationship fields [OK]

Hint: Verify relationship fields match exactly to fix totals [OK]

Common Mistakes:

• Ignoring field mismatches in relationships
• Assuming refresh fixes relationship logic
• Confusing relationships with joins or merges

5. You have three tables: Sales (with SaleID, ProductID, DateID), Products (with ProductID, ProductName), and Dates (with DateID, Date). How should you set up relationships to analyze total sales by product name and date?

hard

A. Create a relationship from Products to Dates directly

B. Join all three tables into one large table before analysis

C. Create relationships from Sales to Products on ProductID and from Sales to Dates on DateID

D. Create relationships from Products to Sales on ProductName and from Dates to Sales on Date

Solution

1. Step 1: Identify keys for relationships

   Sales table contains foreign keys ProductID and DateID linking to Products and Dates tables respectively.

2. Step 2: Set relationships on matching keys

   Create relationships from Sales to Products on ProductID and from Sales to Dates on DateID to enable combined analysis.

3. Step 3: Eliminate incorrect options

   Joining all tables into one is not necessary; relating Products to Dates directly lacks a direct key; using ProductName and Date for relationships are incorrect keys.

4. Final Answer:

   Create relationships from Sales to Products on ProductID and from Sales to Dates on DateID -> Option C

5. Quick Check:

   Relationships use foreign keys from fact to dimension tables [OK]

Hint: Link fact table keys to dimension tables for analysis [OK]

Common Mistakes:

• Trying to relate dimension tables directly without fact table
• Using descriptive fields instead of keys for relationships
• Joining tables unnecessarily instead of relating