Forum Discussion
USERNAME() returning weird e-mail format
I'm using USERNAME() to check against a security table for Row Level Security (RLS) based on the user.
For one of the users, I'm getting a weird e-mail format returned: live.com#[email protected]
Didn't figure this out until I explicitly put USERNAME() in a card on the report to see what was being used.
Has anyone seen that? Is this going to happen for all users that have outlook.com e-mail addresses?
Using the "live.com#[email protected]" in my look up table doesn't work, so I'm thinking I have to filter out any text before a # in an e-mail address to correct for this weird behavior. Any insights to this would help me with configuring my access table for others.
Thanks for the tip on using gmail. I was able to test with the "live.com#[email protected]".
USERPRINCIPALNAME() returns the same "live.com#[email protected]" as USERNAME(). I saw some online documentation saying the same, that USERNAME() behaves differently on the PowerBI Service than on Desktop, but is the same as USERPRINCIPALNAME().
It looks like my table entry of "live.com#[email protected]" does work though, so that is a workaround if needed, but very clunky. So what I did was strip that Azure prefix out before the compare to get it to work. Here's the code I use to limit the Country view:
[Reseller_Country] =
LOOKUPVALUE(
ReportUsers[Country],
ReportUsers[Microsoft Account],
MID(USERNAME(),
FIND ("#", USERNAME(), 1,0) + 1,
LEN (USERNAME())- FIND("#", USERNAME(), 1,0)
),
ReportUsers[Country],
[Reseller_Country]
)Now I don't have to worry about any random prefixes being added to the username e-mail address by Azure. Thanks for the help.
I guess you can't put e-mails into the message body. I just posted a reply that disappeared. Sucks.
So basically, I've determined there are 3 different e-mail formats that get return: 1) regular, 2) live.com# prefix, and 3) abc_workmail.com#EXT#(at)onmail.mail.com
It's a pain to figure out which one is going to show up, so I decided to just fix the e-mail back to regular and not have to mess with the special characters inserted. Here's an example of my formula used in the RLS role:
[Region] =
VAR findpound = FIND("#", USERPRINCIPALNAME(), 1, 0)
VAR CleanUserName = MID(USERPRINCIPALNAME(),
FIND ("#", USERPRINCIPALNAME(), 1, 0) + 1,
LEN (USERPRINCIPALNAME()) - findpound)
VAR CleanedUserName = IF(LEFT(CleanUserName,4)="EXT#",
SUBSTITUTE(LEFT(USERPRINCIPALNAME(),
findpound-1), "_","@"),CleanUserName)
RETURN
LOOKUPVALUE(
Region[Region],
Region[Country],
LOOKUPVALUE(
ReportUsers[Country],
ReportUsers[Account],
CleanedUserName),
Region[Region],
[Region]
)
20 Replies
- Hi there
The reason that it appears that way is because that is how the display name is stored in Azure Active Directory.
I would suggest changing it to USERPRINCIPALNAME() which is for the Power BI Service.
USERNAME() is for when you are inside a domain.
And finally in your lookup table store just the email address [email protected] it will correctly resolve it with the USERPRINCIPALNAME() lookupThanks, I'll try USERPRINCIPALNAME() and see if that works. Need the user with that e-mail to verify. Looks like you can't emulate it using Test as Role on the PowerBI Service.
- Hi there,
If you have a gmail or hotmail address you could test it yourself.
You are correct in that the test a role doesn't work
