Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I use the LOOKUP formula in conjunction with the PATH formula to create a Hierarchy for my RLS. Almost two years solid with no issues, but today - I ran accross this error and am having trouble correcting it the right way.
Currently using:
Org Level 1 = LOOKUPVALUE('Active Directory'[Employee Email],'Active Directory'[Employee Name],PATHITEM('Active Directory'[Hierarchy],4,TEXT))
I attempted a fix in which I learned the potential issue. In the power query, I filtered out NULLS in the name column. This corrected the error, but completely threw off my Org Level columns. For ex. in the first row I would expect that Org Level 2 would be Kara, however after I filtered out the NULLS it was not Kara it was just blank. Kara was in Org Level 4, which doesn't make any sense.
So the issue potentially has something to do with NULLS in [Employee Name] data?
Any ideas?
Trevor
Solved! Go to Solution.
@tjlundquist1 , Try a new column like
Org Level 1 =
var _1 = PATHITEM('Active Directory'[Hierarchy],4,TEXT)
return
maxx(filter('Active Directory' ,'Active Directory'[Employee Name] =_1), 'Active Directory'[Employee Email])
@tjlundquist1 , Try a new column like
Org Level 1 =
var _1 = PATHITEM('Active Directory'[Hierarchy],4,TEXT)
return
maxx(filter('Active Directory' ,'Active Directory'[Employee Name] =_1), 'Active Directory'[Employee Email])
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
63 | |
62 | |
52 | |
39 | |
24 |
User | Count |
---|---|
84 | |
57 | |
45 | |
42 | |
37 |