Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Using USERPRINCIPALNAME() to give users a personal view of a report. Works great.
Reorganised the report so that the source is now an online PBI dataset and now when in PBI desktop the function returns the long alphanumeric string id instead of user@xxx.com. Still works fine in the Service but its annoying for development as I cannot test the report properley without publishing.
Anyone else come across this? Any workaround?
Solved! Go to Solution.
@Anonymous
You can typically override the result returned by USERPRINCIPALNAME() in Power BI Desktop by selecting "Test As" from the Security section of Modelling tab - and entering any target email.
Since you are connecting to a shared dataset - these options are disabled. Given this limitation - the only workaround may be reguarly publish the report to a test/dev PBI service environment online. I don't believe you can override USERPRINCIPALNAME() in PBI desktop when connecting to a shared dataset.
Hi @Anonymous,
Perhaps you can add RLS role to your data model to enable the UPN instead guid id string of user names.
For detailed descriptions, you can take a look at the following blog that told about similar issues(if it helps for your scenario) :
Using Username() in DAX with Row-Level Security
Regards,
Xiaoxin Sheng
Hi @Anonymous,
Perhaps you can add RLS role to your data model to enable the UPN instead guid id string of user names.
For detailed descriptions, you can take a look at the following blog that told about similar issues(if it helps for your scenario) :
Using Username() in DAX with Row-Level Security
Regards,
Xiaoxin Sheng
@Anonymous
You can typically override the result returned by USERPRINCIPALNAME() in Power BI Desktop by selecting "Test As" from the Security section of Modelling tab - and entering any target email.
Since you are connecting to a shared dataset - these options are disabled. Given this limitation - the only workaround may be reguarly publish the report to a test/dev PBI service environment online. I don't believe you can override USERPRINCIPALNAME() in PBI desktop when connecting to a shared dataset.