Forum Discussion
Power BI On Premise - Applying Row Level Security
Please check that you have done the following step.
After the report is uploaded to PBIRS;
- Go to the PBIRS folder that pbix is residing.
Each pbix is shown in a tiled view with 3 dots on the top right hand corner.
Click those 3 dots and select "Manage" -> "Row-level security"
Click "Add Member"
Here, you have to add AD usernames or AD groups to the security-role you defined in PB Desktop. - Instead of adding each user/role, I think "Everyone" group can be added here, so that Row Level Security can appropriately filter rows for each user.
- Go to the PBIRS folder that pbix is residing.
I found out, that Power BI Report Server Version 1.4.6969.7395 (January 2019) converts the result of DAX function USERNAME() to
In PowerBI Desktop create a card visual that only shows the a measure called USERN.
Measure USRN looks like:
USRN:=username()
Deploy this report to PowerBI Report Server (January 2019) and you will see the result is:
User@upnsuffix and NOT Domain\username
PowerBI_Develop wrote:I found out, that Power BI Report Server Version 1.4.6969.7395 (January 2019) converts the result of DAX function USERNAME() to
USERPRINCIPALNAME()
In PowerBI Desktop create a card visual that only shows the a measure called USERN.
Measure USRN looks like:
USRN:=username()
Deploy this report to PowerBI Report Server (January 2019) and you will see the result is:
User@upnsuffix and NOT Domain\username
Notice the same thing can someone confirm please if this is a bug and if it was raised to Microsoft
Thanks
Any update on this? It appears that username() and userprincipalname() are still routing to the same result once published.
This behavior was a design choice, both username and userprincipalname returns the value of userprincipalname. This is consistent with the experience with reports published to powerbi service.
Thanks
-Boreki