Testing RLS in Desktop in Power BI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a role filter for the 'Region' column.

Power BI

FILTER('Sales', 'Sales'[Region] = [1])

Drag options to blanks, or click blank then click option'

A"East"

B"South"

C"North"

D"West"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to put quotes around the region name.

Using a column name instead of a string value.

The role filter uses the exact region name as a string. Here, "South" is the correct filter value.

2fill in blank

medium

Complete the DAX expression to create a calculated table for RLS testing.

Power BI

TestTable = FILTER(ALL('Sales'), 'Sales'[Country] = [1])

Drag options to blanks, or click blank then click option'

A"USA"

B"Canada"

C"Mexico"

D"Brazil"

Attempts:

3 left

💡 Hint

Common Mistakes

Not using ALL to remove filters.

Using a column reference instead of a string.

The calculated table filters all sales data to only include rows where the Country is "USA".

3fill in blank

hard

Fix the error in the DAX expression for role filter.

Power BI

FILTER('Sales', 'Sales'[Year] [1] 2023)

Drag options to blanks, or click blank then click option'

A>=

B==

C=>

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '=' for equality.

Reversing the operator symbols.

In DAX, the correct operator for 'greater than or equal to' is >=, not => or ==.

4fill in blank

hard

Fill both blanks to create a DAX role filter that limits data to the current user and year.

Power BI

FILTER('Sales', 'Sales'[UserEmail] = USERPRINCIPALNAME() && 'Sales'[Year] [1] [2])

Drag options to blanks, or click blank then click option'

A=

B2024

C>=

D<=

Attempts:

3 left

💡 Hint

Common Mistakes

Using logical OR instead of AND.

Using incorrect comparison operators.

The filter checks that the UserEmail matches the logged-in user and the Year equals 2024.

5fill in blank

hard

Fill all three blanks to create a DAX measure that counts sales filtered by user and region.

Power BI

SalesCount = CALCULATE(COUNTROWS('Sales'), FILTER('Sales', 'Sales'[UserEmail] = [1] && 'Sales'[Region] = [2] && 'Sales'[Year] [3] 2023))

Drag options to blanks, or click blank then click option'

AUSERPRINCIPALNAME()

B"East"

C=

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around USERPRINCIPALNAME().

Using wrong comparison operators.

This measure counts rows where the user email matches the logged-in user, the region is "East", and the year is 2023.

Practice

1. What is the main purpose of using View as Roles in Power BI Desktop?

easy

A. To preview how data looks for different user roles with Row-Level Security applied

B. To create new data tables in the model

C. To export reports to PDF format

D. To refresh data from the source

Solution

1. Step 1: Understand the function of 'View as Roles'

   This feature lets you simulate the data view of different security roles without publishing the report.

2. Step 2: Identify the purpose in context

   It helps verify that Row-Level Security (RLS) filters are working correctly by showing what data each role can access.

3. Final Answer:

   To preview how data looks for different user roles with Row-Level Security applied -> Option A

4. Quick Check:

   View as Roles previews RLS effects [OK]

Hint: Use 'View as Roles' to test RLS before publishing [OK]

Common Mistakes:

• Confusing 'View as Roles' with data refresh
• Thinking it creates new tables
• Assuming it exports reports

2. Which of the following is the correct way to define a role filter in Power BI Desktop using DAX?

easy

A. Sales[Region] = "West"

B. FILTER(Sales, Sales[Region] = "West")

C. Sales[Region] == "West"

D. Sales.Region = 'West'

Solution

1. Step 1: Recall DAX filter syntax for roles

   Role filters use a Boolean expression like Table[Column] = "Value" to filter rows.

2. Step 2: Evaluate each option

   Sales[Region] = "West" uses correct DAX syntax with single equals and double quotes. FILTER(Sales, Sales[Region] = "West") is a function, not a direct filter expression. Sales[Region] == "West" uses double equals which is invalid in DAX. Sales.Region = 'West' uses dot notation and single quotes, which is incorrect.

3. Final Answer:

   Sales[Region] = "West" -> Option A

4. Quick Check:

   DAX role filter uses single equals and double quotes [OK]

Hint: Use single equals and double quotes in role filters [OK]

Common Mistakes:

• Using double equals (==) instead of single equals (=)
• Using dot notation instead of bracket notation
• Using FILTER function inside role filter

3. Given a role with filter Customers[Country] = "USA", what will COUNTROWS(Customers) return when viewing as this role if the Customers table has 100 rows with 30 from USA?

medium

A. 100

B. 70

C. 30

D. 0

Solution

1. Step 1: Understand the role filter effect

   The role filter limits visible rows to those where Country = "USA", so only 30 rows remain visible.

2. Step 2: Apply filter to COUNTROWS

   COUNTROWS counts only visible rows under the role filter, so it returns 30.

3. Final Answer:

   30 -> Option C

4. Quick Check:

   Role filter limits rows, COUNTROWS returns filtered count [OK]

Hint: COUNTROWS respects RLS filters, returns visible rows only [OK]

Common Mistakes:

• Ignoring role filter and returning total rows
• Confusing filtered out rows with visible rows
• Assuming COUNTROWS returns zero if filtered

4. You defined a role with filter Orders[Amount] > 1000 but when testing with 'View as Roles', all data is visible. What is the most likely cause?

medium

A. The role filter syntax is incorrect and ignored

B. The Orders table has no rows with Amount > 1000

C. The 'View as Roles' feature is disabled in Power BI Desktop

D. You did not assign the role to any user

Solution

1. Step 1: Check role assignment

   In Power BI Desktop, roles must be assigned to users in the service, but 'View as Roles' simulates roles without user assignment. However, if you select 'View as Roles' and no role is selected, no filter applies.

2. Step 2: Verify role filter syntax and data

   The syntax Orders[Amount] > 1000 is correct. If data had no matching rows, filtered data would be empty, not all visible.

3. Final Answer:

   You did not assign the role to any user -> Option D

4. Quick Check:

   Role must be selected in 'View as Roles' to apply filter [OK]

Hint: Select the role in 'View as Roles' to apply filters [OK]

Common Mistakes:

• Assuming syntax error when filter is correct
• Not selecting role in 'View as Roles' dialog
• Thinking 'View as Roles' is disabled by default

5. You have two roles: RoleA filters Sales[Region] = "East" and RoleB filters Sales[Region] = "West". How can you test combined access for a user assigned to both roles in Power BI Desktop?

hard

A. Create a new role with a filter combining both regions and test it

B. Use 'View as Roles' and select both RoleA and RoleB to see combined data

C. Assign the user only to RoleA and test, then switch to RoleB

D. You cannot test combined roles in Power BI Desktop

Solution

1. Step 1: Understand role combination in 'View as Roles'

   Power BI Desktop allows selecting multiple roles simultaneously in 'View as Roles'. The filters combine with OR logic, showing data accessible by any selected role.

2. Step 2: Apply multiple roles selection

   Selecting both RoleA and RoleB will show sales data from both East and West regions combined.

3. Final Answer:

   Use 'View as Roles' and select both RoleA and RoleB to see combined data -> Option B

4. Quick Check:

   Multiple roles combine filters with OR in 'View as Roles' [OK]

Hint: Select multiple roles in 'View as Roles' to test combined access [OK]

Common Mistakes:

• Thinking roles combine with AND logic
• Creating new roles unnecessarily
• Believing combined roles cannot be tested