Creating calculated fields in Tableau - Quick Revision & Summary

Recall & Review

beginner

What is a calculated field in Tableau?

A calculated field is a new field created by using a formula to combine or transform existing data fields. It helps you analyze data in ways not directly available in your original data.

beginner

How do you create a calculated field in Tableau?

Right-click in the Data pane and select 'Create Calculated Field'. Then enter your formula in the dialog box and click OK to add it to your data.

intermediate

Which of these is a valid Tableau calculated field formula?

SUM([Sales]) / COUNT([Orders])

This formula calculates the average sales per order by dividing the total sales by the number of orders. It is valid because it uses aggregation functions correctly.

beginner

What happens if you use a calculated field with an error in Tableau?

Tableau shows an error message and does not create the field. You need to fix the formula syntax or logic before it can be used.

beginner

Why use calculated fields instead of changing the original data?

Calculated fields let you create new insights without changing the original data source. This keeps data safe and lets you experiment with different analyses easily.

What is the first step to create a calculated field in Tableau?

A Right-click in the Data pane and select 'Create Calculated Field'

B Edit the original data source

C Drag a field to the Rows shelf

D Click 'Show Me' and select a chart

You start by right-clicking in the Data pane and choosing 'Create Calculated Field' to open the formula editor.

Which of these is a valid aggregation function in Tableau calculated fields?

A MULTIPLY()

B ADD()

C SUM()

D DIVIDE()

SUM() is a valid aggregation function. ADD(), MULTIPLY(), and DIVIDE() are not Tableau functions.

What does this calculated field do?

IF [Profit] > 0 THEN 'Good' ELSE 'Bad' END

A Calculates total profit

B Labels profits as 'Good' if positive, otherwise 'Bad'

C Filters out negative profits

D Creates a sum of profits

This formula checks if Profit is positive and labels it 'Good', otherwise 'Bad'.

If a calculated field formula has a syntax error, what will Tableau do?

A Show an error and prevent creation

B Create the field anyway

C Ignore the error and use default values

D Automatically fix the error

Tableau shows an error message and stops you from creating the field until the error is fixed.

Why is it better to use calculated fields instead of changing the original data?

A Calculated fields automatically clean data

B Calculated fields run faster than original data

C Original data cannot be edited in Tableau

D Keeps original data safe and allows flexible analysis

Calculated fields let you create new insights without altering the original data, keeping it safe and flexible.

Explain how to create a calculated field in Tableau and give an example formula.

Think about the steps you take in Tableau to add new data calculations.

Describe why calculated fields are useful and how they differ from changing the original data.

Consider the benefits of keeping original data intact.

Practice

1. What is the main purpose of creating a calculated field in Tableau?

easy

A. To change the color of a chart

B. To import data from external sources

C. To create new data values based on existing data using formulas

D. To delete rows from the data source

Solution

1. Step 1: Understand what calculated fields do

   Calculated fields allow you to create new data by applying formulas to existing data.

2. Step 2: Compare options to this definition

   Only To create new data values based on existing data using formulas describes creating new data values using formulas, which matches the purpose of calculated fields.

3. Final Answer:

   To create new data values based on existing data using formulas -> Option C

4. Quick Check:

   Calculated fields = new data from formulas [OK]

Hint: Calculated fields create new data from old data using formulas [OK]

Common Mistakes:

• Confusing calculated fields with data import
• Thinking calculated fields change visuals only
• Assuming calculated fields delete data

2. Which of the following is the correct syntax to create a calculated field that adds 10 to the value of the field Sales?

easy

A. SUM(Sales) + 10

B. [Sales] + 10

C. {Sales} + 10

D. Sales + 10

Solution

1. Step 1: Recall Tableau field reference syntax

   In Tableau, fields are referenced inside square brackets like [Sales].

2. Step 2: Check each option's syntax

   [Sales] + 10 uses [Sales] + 10, which is correct. Sales + 10 misses brackets, C uses curly braces which are incorrect here, and A uses aggregation which is not needed for simple addition.

3. Final Answer:

   [Sales] + 10 -> Option B

4. Quick Check:

   Field names need brackets in formulas [OK]

Hint: Use square brackets around field names in formulas [OK]

Common Mistakes:

• Omitting square brackets around field names
• Using curly braces instead of brackets
• Adding aggregation unnecessarily

3. Given the calculated field formula IF [Profit] > 0 THEN 'Profit' ELSE 'Loss' END, what will be the result for a record where [Profit] is -50?

medium

A. 'Loss'

B. 'Profit'

C. 50

D. Error

Solution

1. Step 1: Understand the IF condition

   The formula checks if [Profit] is greater than 0. If yes, returns 'Profit', else returns 'Loss'.

2. Step 2: Apply the condition to the value -50

   Since -50 is not greater than 0, the ELSE part applies, so the result is 'Loss'.

3. Final Answer:

   'Loss' -> Option A

4. Quick Check:

   Profit > 0? No, so 'Loss' [OK]

Hint: Check IF condition carefully for each value [OK]

Common Mistakes:

• Confusing greater than with less than
• Expecting numeric output instead of text
• Ignoring ELSE clause

4. Identify the error in this calculated field formula: IF [Sales] > 1000 THEN 'High' ELSE 'Low'

medium

A. Incorrect use of square brackets around Sales

B. No error, formula is correct

C. Using text values instead of numbers

D. Missing END keyword to close IF statement

Solution

1. Step 1: Review IF statement syntax in Tableau

   Tableau IF statements must end with the keyword END to close the block.

2. Step 2: Check the given formula

   The formula lacks the END keyword at the end, so it will cause a syntax error.

3. Final Answer:

   Missing END keyword to close IF statement -> Option D

4. Quick Check:

   IF statements need END keyword [OK]

Hint: Always end IF statements with END [OK]

Common Mistakes:

• Forgetting END keyword in IF formulas
• Misplacing square brackets
• Confusing text and numeric outputs

5. You want to create a calculated field that categorizes sales into three groups: 'Low' for sales below 500, 'Medium' for sales between 500 and 1000, and 'High' for sales above 1000. Which formula correctly implements this?

hard

A. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] <= 1000 THEN 'Medium' ELSE 'High' END

B. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] < 1000 THEN 'Medium' ELSE 'High' END

C. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] < 1000 THEN 'Medium' ELSEIF [Sales] > 1000 THEN 'High' END

D. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] <= 1000 THEN 'Medium' ELSEIF [Sales] > 1000 THEN 'High'

Solution

1. Step 1: Understand the sales ranges

   Sales below 500 = 'Low', 500 to 1000 inclusive = 'Medium', above 1000 = 'High'.

2. Step 2: Check each formula for correct conditions and syntax

   IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] <= 1000 THEN 'Medium' ELSE 'High' END correctly uses ELSEIF with <= 1000 for 'Medium' and ends with END. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] < 1000 THEN 'Medium' ELSE 'High' END excludes 1000 from 'Medium'. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] < 1000 THEN 'Medium' ELSEIF [Sales] > 1000 THEN 'High' END has an extra ELSEIF but no final ELSE. IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] <= 1000 THEN 'Medium' ELSEIF [Sales] > 1000 THEN 'High' misses END keyword.

3. Final Answer:

   IF [Sales] < 500 THEN 'Low' ELSEIF [Sales] <= 1000 THEN 'Medium' ELSE 'High' END -> Option A

4. Quick Check:

   Ranges inclusive and END keyword correct [OK]

Hint: Use ELSEIF and END; include boundary with <= for ranges [OK]

Common Mistakes:

• Missing END keyword
• Incorrect boundary conditions (e.g., excluding 1000)
• Using multiple ELSEIF without final ELSE