Tableau-Desktop-Found Connecting to and Preparing Data Practice Question
Exhibit
ERROR: 'The relationship cannot be created because the types of the joining fields do not match.'
Refer to the exhibit. You are trying to establish a relationship between two tables, but receive this error. What is the best way to fix this?
⚠ Common exam trap
Candidates often try to change the data type of the underlying source files directly or ignore the mismatch, assuming Tableau will automatically cast fields during a relationship setup.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a calculation to cast both fields to the same type
Tableau's relationship engine requires consistent data types for the related fields. If one is an integer and the other is a string, the engine cannot establish a valid relationship. This is a common issue when pulling data from disparate systems. The solution is to create a calculated field to cast the data to a matching type, ensuring logical consistency for the underlying query engine to execute successfully.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the database schema of the original source
Why it's wrong here
While changing the schema works, it is often outside the scope of a Tableau user's permissions and can have negative impacts on other applications using the same database. It is much better to handle the type mismatch within the Tableau environment using calculations or metadata changes.
- ✓
Use a calculation to cast both fields to the same type
Why this is correct
Creating a calculated field, such as STR([ID]) or INT([ID]), allows you to align the data types within Tableau without needing to modify the source database. This is the standard, best-practice approach for resolving type mismatches in a non-destructive manner that keeps your workbook flexible and functional.
- ✗
Delete the Relationship and use a join instead
Why it's wrong here
Joins also require matching data types for the join key. Switching to a join will not solve the underlying issue of incompatible data formats. You would still face the same error because the database engine cannot compare a string to an integer, regardless of the integration method used.
- ✗
Restart the Tableau instance
Why it's wrong here
Restarting the software does not resolve structural metadata errors. This is a data preparation issue caused by incompatible types, not a software glitch. Troubleshooting by restarting is a waste of time and does not address the core requirement for aligning data fields as defined by the system.
About these practice questions
This Tableau-Desktop-Found question is part of Courseiva's 126-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Tableau (Salesforce) exam blueprint
This Tableau-Desktop-Found practice question is part of Courseiva's free Tableau (Salesforce) certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Tableau-Desktop-Found exam.