Resolve issue with username data for RLS

[breben]

Trying to implement RLS for a report.  The user name data in the data set is only "Firstname Lastname".  Using USERNAME() won't help as it returns the domain\logonname, which the logonname won't be the same data as First Last name.  Same for USERPRINCIPALNAME().  Do I need to create a mapping somewhere of each user's First and Last and tie it to their USERNAME or USERPRINCIPALNAME to make this work? Is there a better way?  thanks   

[parry2k]

@breben for the xls and it will pass it on to your connected table. You can check RLS-related videos on my channel just to get a basic understanding of where to apply the role

[breben]

I'm still struggling on the DAX portion.  The native UserName() and UserPrincipalName() functions won't work since my dataset only has the user's full name (Joe Smith) and neither username or UPN in this scenario contain the full name, only an abbreviation of their full name (jsmith1234@company.com).  I have an XLS where I have defined the user's full name and the related UPN and have created the relationship to the database dataset but still struggling on how to implement this lookup in the report. 

[parry2k]

@breben that is the way to crate the mapping table to make it work, or extract first name and last name from userprincipalname() if email and first, last name use the standard logic.

[breben]

OK that's what I figured.  So from the database datasource, the user name is "Joe Smith".  I have created an .XLS for now with two columns, one for the full name and the other for the UPN.  So, "Joe Smith" in the first column and jsmith1234@company.com in the second column. 

In PBI I created the relationship between the database and the .XMS, with the full name as the linked field.

Now when I create the role in PBI, am I creating the rule for the database source table which has the full name, or am I creating the rule for the .XLS, which is where the mapping data is held?  That's where I am currently confused.