Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
planbitionbi
Frequent Visitor

Row level security with user email -> Multiple User ID with same e-mail to filter on

Hi all!

 

I have succesfully implemented row level security using the guide:

https://www.youtube.com/watch?v=Sge_g9hTXWE&feature=emb_logo&ab_channel=PragmaticWorks

 

Now the only issue is that I can have multiple users (userID's) with the same email adress and my DAX Filter on the table I have implemented RLS on expects a singel UserID. How can I change this DAX Formula in a way that multiple USerID's can be the input of the filter.

 

DAX Formule on my CustomerStructure table:

[ID] IN SELECTCOLUMNS(
FILTER(
Security_User_CustomerStructure,
Security_User_CustomerStructure[PersonID] = LOOKUPVALUE(Security_Users[PersonID], Security_Users[Email], USERNAME() )
),
"ID", [CustomerStructureID]
)

 

Printscreens:

planbitionbi_0-1610442260722.pngplanbitionbi_1-1610442287192.png

 

 

1 ACCEPTED SOLUTION

Hi @planbitionbi ,

 

Please refer to the following measure:

[ID]
        IN SELECTCOLUMNS (
            FILTER (
                Security_User_CustomerStructure,
                Security_User_CustomerStructure[PersonID]
                    IN CALCULATETABLE (
                        VALUES ( Security_Users[PersonID] ),
                        FILTER ( Security_Users, Security_Users[Email] = USERPRINCIPALNAME () )
                    )
            ),
            "ID", [CustomerStructureID]
        )

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards,

Dedmon Dai

View solution in original post

3 REPLIES 3
planbitionbi
Frequent Visitor

Hi!

 

Thanks a lot for your feedback. Unfortunately it's throwing an error like below. Can you see why it's wrong? Something with the IN clause:

 

planbitionbi_0-1610615667143.png

 

Hi @planbitionbi ,

 

Please refer to the following measure:

[ID]
        IN SELECTCOLUMNS (
            FILTER (
                Security_User_CustomerStructure,
                Security_User_CustomerStructure[PersonID]
                    IN CALCULATETABLE (
                        VALUES ( Security_Users[PersonID] ),
                        FILTER ( Security_Users, Security_Users[Email] = USERPRINCIPALNAME () )
                    )
            ),
            "ID", [CustomerStructureID]
        )

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards,

Dedmon Dai

v-deddai1-msft
Community Support
Community Support

Hi @planbitionbi ,

 

I suggest you use USERPRINCIPALNAME ( ) instead of USERNAME() and you can change the dax to :

 

[ID] IN SELECTCOLUMNS(
FILTER(
Security_User_CustomerStructure,
Security_User_CustomerStructure[PersonID] IN CALCULATETABLE(VALUES(Security_Users[PersonID]),FILTER(Security_Users,Security_Users[Email] = USERPRINCIPALNAME())),
"ID", [CustomerStructureID]
)

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards,

Dedmon Dai

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.