Logical Functions
This article introduces logical functions and their uses in Tableau. It also demonstrates how to create a logical calculation using an example.
Why use logical calculations
Logical calculations allow you to determine whether a certain condition is true or false (Boolean logic). For example, you might want to categorise values based on certain cut-offs.
A logical calculation might look something like this:
IF [Profit] > 0
THEN 'Profitable'
ELSEIF [Profit] = 0 THEN 'Break even'
ELSE 'Loss'
END
Logical functions and operators available in Tableau
AND
Syntax | <expr1> AND <expr2> |
Definition | Performs a logical conjunction on two expressions. (If both sides are true, the logical test returns true.) |
Output | Boolean (true or false) |
Example | IF [Season] = "Spring" AND "[Season] = "Fall" “If both (Season = Spring) and (Season = Autumn) are true simultaneously, then return ‘It's the apocalypse and footwear doesn't matter’.” |
Notes | Often used with IF and IIF. See also NOT and OR. If both expressions are If you create a calculation in which the result of an Note: The |
CASE
Syntax | CASE <expression>
|
Output | Depends on data type of the <then> values. |
Definition | Evaluates the |
Example |
"Look at the Season field. If the value is Summer, then return Sandals. If the value is Winter, then return Boots. If none of the options in the calculation match what is in the Season field, return Sneakers." |
Notes | Used with WHEN, THEN, ELSE and END. Tip: Many times you can use a group to get the same results as a complicated CASE function, or use CASE to replace native grouping functionality, such as in the previous example. You may want to test which is more performant for your scenario. |
ELSE
Syntax | CASE <expression>
|
Definition | An optional piece of an IF or CASE expression used to specify a default value to return if none of the tested expressions are true. |
Example | IF [Season] = "Summer" THEN 'Sandals' CASE [Season] |
Notes | Used with CASE, WHEN, IF, ELSEIF, THEN and END
|
ELSEIF
Syntax | [ELSEIF <test2> THEN <then2>] |
Definition | An optional piece of an IF expression used to specify additional conditions beyond the initial IF. |
Example | IF [Season] = "Summer" THEN 'Sandals' |
Notes | Used with IF, THEN, ELSE and END
Unlike |
END
Definition | Used to close an IF or CASE expression. |
Example | IF [Season] = "Summer" THEN 'Sandals' "If Season = Summer, then return Sandals. If not, look at the next expression. If Season = Winter, then return Boots. If neither of the expressions are true, return Sneakers." CASE [Season] "Look at the Season field. If the value is Summer, then return Sandals. If the value is Winter, then return Boots. If none of the options in the calculation match what is in the Season field, return Sneakers." |
Notes |
IF
Syntax | IF <test1> THEN <then1> |
Output | Depends on data type of the <then> values. |
Definition | Tests a series of expressions and returns the |
Example | IF [Season] = "Summer" THEN 'Sandals' "If Season = Summer, then return Sandals. If not, look at the next expression. If Season = Winter, then return Boots. If neither of the expressions are true, return Sneakers." |
Notes |
IFNULL
Syntax | IFNULL(expr1, expr2) |
Output | Depends on the data type of the <expr> values. |
Definition | Returns |
Example | IFNULL([Assigned Room], "TBD") "If the Assigned Room field isn't null, return its value. If the Assigned room field is null, return TBD instead." |
Notes | Compare with ISNULL. See also ZN. |
IIF
Syntax | IIF(<test>, <then>, <else>, [<unknown>]) |
Output | Depends on the data type of the values in the expression. |
Definition | Checks whether a condition is met (<test> ) and returns <then> if the test is true, <else> if the test is false and an optional value for <unknown> if the test is null. If the optional unknown isn't specified, IIF returns null. |
Example | IIF([Season] = 'Summer', 'Sandals', 'Other footwear') "If Season = Summer, then return Sandals. If not, return Other footwear" IIF([Season] = 'Summer', 'Sandals', "If Season = Summer, then return Sandals. If not, look at the next expression. If Season = Winter, then return Boots. If neither are true, return Sneakers." IIF('Season' = 'Summer', 'Sandals', "If Season = Summer, then return Sandals. If not, look at the next expression. If Season = Winter, then return Boots. If none of the expressions are true, return Sneakers." |
Notes |
That is to say, in the calculation below, the result will be Red, not Orange, because the expression stops being evaluated as soon as A=A is evaluated as true:
|
IN
Syntax | <expr1> IN <expr2> |
Output | Boolean (true or false) |
Definition | Returns TRUE if any value in <expr1> matches any value in <expr2> . |
Example | SUM([Cost]) IN (1000, 15, 200) "Is the value of the Cost field 1000, 15 or 200?" [Field] IN [Set] "Is the value of the field present in the set?" |
Notes | The values in See also WHEN. |
ISDATE
Syntax | ISDATE(string) |
Output | Boolean (true or false) |
Definition | Returns true if a <string> is a valid date. The input expression must be a string (text) field. |
Example | ISDATE("2018-09-22") "Is the string 2018-09-22 a properly formatted date?" |
Notes | What is considered a valid date depends on the locale(Link opens in a new window) of the system evaluating the calculation. For example: In the USA:
In the UK:
|
ISNULL
Syntax | ISNULL(expression) |
Output | Boolean (true or false) |
Definition | Returns true if the |
Example | ISNULL([Assigned Room]) "Is the Assigned Room field null?" |
Notes | Compare with IFNULL. See also ZN. |
MAX
Syntax | MAX(expression) or MAX(expr1, expr2) |
Output | Same data type as the argument, or NULL if any part of the argument is null. |
Definition | Returns the maximum of the two arguments, which must be of the same data type.
|
Example | MAX(4,7) = 7 |
Notes | For strings
For database data sources, the For dates For dates, the As an aggregation
As a comparison
See also |
MIN
Syntax | MIN(expression) or MIN(expr1, expr2) |
Output | Same data type as the argument, or NULL if any part of the argument is null. |
Definition | Returns the minimum of the two arguments, which must be of the same data type.
|
Example | MIN(4,7) = 4 |
Notes | For strings
For database data sources, the For dates For dates, the As an aggregation
As a comparison
See also |
NOT
Syntax | NOT <expression> |
Output | Boolean (true or false) |
Definition | Performs logical negation on an expression. |
Example | IF NOT [Season] = "Summer" "If Season doesn't equal Summer, then return Don't wear sandals. If not, return Wear sandals." |
Notes |
OR
Syntax | <expr1> OR <expr2> |
Output | Boolean (true or false) |
Definition | Performs a logical disjunction on two expressions. |
Example | IF [Season] = "Spring" OR [Season] = "Fall" "If either (Season = Spring) or (Season = Fall) is true, then return Sneakers." |
Notes | Often used with IF and IIF. See also AND and NOT. If either expression is If you create a calculation that displays the result of an Note: The |
THEN
Syntax | IF <test1> THEN <then1>
|
Definition | A required part of an IF , ELSEIF or CASE expression, used to define what result to return if a specific value or test is true. |
Example | IF [Season] = "Summer" THEN 'Sandals' "If Season = Summer, then return Sandals. If not, look at the next expression. If Season = Winter, then return Boots. If neither of the expressions are true, return Sneakers." CASE [Season] "Look at the Season field. If the value is Summer, then return Sandals. If the value is Winter, then return Boots. If none of the options in the calculation match what is in the Season field, return Sneakers." |
Notes |
WHEN
Syntax | CASE <expression>
|
Definition | A required part of a CASE expression. Finds the first <value> that matches <expression> and returns the corresponding <then> . |
Example | CASE [Season] "Look at the Season field. If the value is Summer, then return Sandals. If the value is Winter, then return Boots. If none of the options in the calculation match what is in the Season field, return Sneakers." |
Notes | Used with CASE, THEN, ELSE and END.
CASE <expression> The values that |
ZN
Syntax | ZN(expression) |
Output | Depends on the data type of the <expression> , or 0. |
Definition | Returns <expression> if it isn't null; otherwise returns zero. |
Example | ZN([Test Grade]) "If the test grade isn't null, return its value. If the test grade is null, return 0." |
Notes |
See also ISNULL. |
Note: Some of these are actually logical operators and appear in black, not blue. For more information, see Operator syntax.
CASE is often easier to use than IF or IIF. In many instances, IF, IIF and CASE can be used interchangeably. A CASE statement can always be rewritten as an IF statement, although the CASE function will generally be more concise and may be easier to understand. However, not all IF statements can be written as CASE statements, because each ELSEIF could refer to a different field.
Tip: Let's compare an example using the same logic across these three functions:
CASE | IF | IIF |
CASE [Region] | IF [Region] = 'West' THEN 1 | IIF([Region] = 'West', 1, |
The CASE structure is very simple and easy to write and understand. However, the expression (here, [Region]) cannot be a logical operation, unlike with IF or IIF. Nulls are handled the same for CASE as they are for IF. | The IF THEN structure permits multiple ELSEIF clauses, which makes multiple evaluations much easier than with IIF. Null handling: any unknown (null) results are handled by the same ELSE clause as false results. Here, any region other than the four specified (including null) will be assigned a value of 5. | The IIF structure handles unknown results differently than false results and has a different syntax from IF. The trade-off for specific null handling is nesting, as above, which can be clumsy to write and understand. Null handling: any non-null region other than the four specified will be assigned a value of 5, but a null value will be assigned a 0. |
Note: Often, you can use a group to get the same results as a complicated case function. Test to see whether one option is more performant than the other.
Examples
CASE functions can be useful for scenarios such as realising:
CASE LEFT(DATENAME('weekday',[Order Date]),3)
WHEN 'Sun' THEN 0
WHEN 'Mon' THEN 1
WHEN 'Tue' THEN 2
WHEN 'Wed' THEN 3
WHEN 'Thu' THEN 4
WHEN 'Fri' THEN 5
WHEN 'Sat' THEN 6
END
or giving the end user the ability to select which measure to view in a chart when used with a parameter(Link opens in a new window):
CASE [Choose a Measure]
WHEN "Sales" THEN SUM([Sales])
WHEN "Profit" THEN AVG([Profit])
WHEN "Quantity" THEN COUNT([Quantity])
WHEN "Shipping Cost" THEN MEDIAN([Shipping Cost])
END
Create a logical calculation
Follow along with the steps below to learn how to create a logical calculation.
- In Tableau Desktop, connect to the Sample - Superstore saved data source, which comes with Tableau.
- Navigate to a worksheet.
- From the Data pane, drag State to the Rows shelf.
- From the Data pane, drag Category to the Rows shelf and place it to the right of State.
- From the Data pane, drag Sales to the Columns shelf.
- Select Analysis > Create Calculated Field.
- In the calculation editor that opens, do the following:
- Name the calculated field KPI.
- Enter the following formula:
SUM([Profit]) > 0
This calculation quickly checks if a member is great than zero. If so, it returns true; if not, it returns false.
- When finished, click OK.
- From the Data pane, drag KPI to Colour on the Marks card.
You can now see which categories are losing money in each state.
The new calculated field appears under Measures in the Data pane. Just like your other fields, you can use it in onr or more visualisations.
See Also
Visualise Key Progress Indicators