IF function for conditions in Power BI - Cell-by-Cell Formula Trace

Sample Data

Sales amounts in column A and empty Bonus column B to calculate bonus based on sales.

Cell	Value
A1	Sales
A2	500
A3	1500
A4	800
B1	Bonus
B2
B3
B4

Formula Trace

IF(A2 > 1000, "Bonus", "No Bonus")

Step 1: A2 > 1000

Step 2: 500 > 1000

Step 3: IF(FALSE, "Bonus", "No Bonus")

Cell Reference Map

    A       B
1 | Sales | Bonus |
2 |  500  |       |
3 | 1500  |       |
4 |  800  |       |

Arrow: A2 -> formula condition check

The formula checks the value in cell A2 to decide the bonus.

Result

    A       B
1 | Sales | Bonus    |
2 |  500  | No Bonus |
3 | 1500  |          |
4 |  800  |          |

The formula result "No Bonus" is placed in cell B2 because sales in A2 is 500 which is not greater than 1000.

Sheet Trace Quiz - 3 Questions

What does the condition A2 > 1000 evaluate to when A2 is 500?

A 500

B TRUE

C FALSE

D 1000

Key Result

IF(condition, value_if_true, value_if_false) returns value based on condition TRUE or FALSE.

Practice

1. What does the IF function do in Power BI?

easy

A. Checks a condition and returns one value if true, another if false

B. Calculates the sum of a column

C. Filters rows based on a condition

D. Joins two tables together

Solution

1. Step 1: Understand the purpose of IF

   The IF function evaluates a condition and chooses between two results based on whether the condition is true or false.

2. Step 2: Compare with other options

   Calculating the sum of a column, filtering rows based on a condition, and joining tables describe other functions or operations, not IF.

3. Final Answer:

   Checks a condition and returns one value if true, another if false -> Option A

4. Quick Check:

   IF function = condition check [OK]

Hint: IF returns true-result or false-result based on condition [OK]

Common Mistakes:

• Confusing IF with SUM or FILTER functions
• Thinking IF joins tables
• Assuming IF only returns true values

2. Which of the following is the correct syntax for the IF function in DAX?

easy

A. IF condition then true_result else false_result

B. IF(condition; true_result; false_result)

C. IF{condition, true_result, false_result}

D. IF(condition, true_result, false_result)

Solution

1. Step 1: Recall DAX IF syntax

   The correct syntax uses parentheses and commas: IF(condition, true_result, false_result).

2. Step 2: Identify incorrect syntax

   Using 'then else' keywords, semicolons instead of commas, or braces are invalid in standard DAX syntax.

3. Final Answer:

   IF(condition, true_result, false_result) -> Option D

4. Quick Check:

   DAX IF syntax = parentheses and commas [OK]

Hint: Use parentheses and commas for IF in DAX [OK]

Common Mistakes:

• Using semicolons instead of commas
• Writing IF like a programming language if-then-else
• Using braces {} instead of parentheses

3. Given the DAX measure:

Sales Category = IF(SUM(Sales[Amount]) > 1000, "High", "Low")

What will be the result if the total sales amount is 750?

medium

A. 750

B. "High"

C. "Low"

D. Error

Solution

1. Step 1: Evaluate the condition

   The condition checks if total sales (750) is greater than 1000. 750 > 1000 is false.

2. Step 2: Determine the IF result

   Since the condition is false, the IF function returns the false_result, which is "Low".

3. Final Answer:

   "Low" -> Option C

4. Quick Check:

   750 > 1000 is false, so result = "Low" [OK]

Hint: Check condition result true/false to pick IF output [OK]

Common Mistakes:

• Assuming 750 is greater than 1000
• Returning the numeric value instead of text
• Confusing true and false results

4. Identify the error in this DAX formula:

Discount Status = IF SUM(Sales[Amount]) > 500, "Discount", "No Discount")

medium

A. No error, formula is correct

B. Missing parentheses around the IF arguments

C. Incorrect column name Sales[Amount]

D. Using double quotes instead of single quotes

Solution

1. Step 1: Check IF function syntax

   The IF function requires parentheses enclosing all arguments: IF(condition, true_result, false_result).

2. Step 2: Identify missing parentheses

   The formula lacks opening parentheses after IF and has an extra closing parenthesis at the end.

3. Final Answer:

   Missing parentheses around the IF arguments -> Option B

4. Quick Check:

   IF syntax needs parentheses [OK]

Hint: Always wrap IF arguments in parentheses [OK]

Common Mistakes:

• Forgetting parentheses after IF
• Confusing quotes usage (double quotes are correct here)
• Assuming column name is wrong without checking

5. You want to create a new column that labels sales as "High", "Medium", or "Low" based on Sales[Amount]:
- "High" if amount > 1000
- "Medium" if amount between 500 and 1000 (inclusive)
- "Low" if amount < 500

Which DAX formula correctly uses nested IF functions to achieve this?

hard

A. Sales Level = IF(Sales[Amount] > 1000, "High", IF(Sales[Amount] >= 500 && Sales[Amount] <= 1000, "Medium", "Low"))

B. Sales Level = IF(Sales[Amount] > 1000, "High", IF(Sales[Amount] > 500 && Sales[Amount] < 1000, "Medium", "Low"))

C. Sales Level = IF(Sales[Amount] > 1000, "High", IF(Sales[Amount] >= 500 || Sales[Amount] <= 1000, "Medium", "Low"))

D. Sales Level = IF(Sales[Amount] > 1000, "High", IF(Sales[Amount] > 500 || Sales[Amount] < 1000, "Medium", "Low"))

Solution

1. Step 1: Understand the conditions

   "High" if >1000, "Medium" if between 500 and 1000 inclusive, "Low" if less than 500.

2. Step 2: Check nested IF logic and operators

   Sales Level = IF(Sales[Amount] > 1000, "High", IF(Sales[Amount] >= 500 && Sales[Amount] <= 1000, "Medium", "Low")) correctly uses AND (&&) with >= and <= for the medium range. The other options have incorrect operators or use OR (||) which breaks the logic.

3. Final Answer:

   Sales Level = IF(Sales[Amount] > 1000, "High", IF(Sales[Amount] >= 500 && Sales[Amount] <= 1000, "Medium", "Low")) -> Option A

4. Quick Check:

   Nested IF with correct AND and inclusive bounds [OK]

Hint: Use nested IF with && and inclusive operators for ranges [OK]

Common Mistakes:

• Using OR (||) instead of AND (&&) for range checks
• Not including equal signs for inclusive ranges
• Incorrect logical operators causing wrong labels