Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hello guys,
I'm starting in Power BI (desktop) and would like to help.
I saw that we could create security levels through groups and allocate users to these groups. But I would like to define each user parameter within a table ... Example : I created a security table which has the user field and region ... After I create the group would like to seek the parameters in this table ...
Example : [Region] = here to get the user accessing this and get the region that he should see in the table
Does anyone know how we can do this ?
Thank you,
LR Feltz
Solved! Go to Solution.
Hi LRfeltz,
1. Here we cant set like Tableau, this is first thing.
2. second the security level totally based and depending on cloud.
3. In server Dataset level u could find the option like security click that one there u could see the Rules tab, under this u could right your DAX query.
Note:
Username() = domain/userloginname
Thanks for the help guys !
I will apply the solutions suggested by you.
thank you!
Hello Friend.
To make data segmentation , follow the steps image .
Comments:
1 - the RLS rules only work on dashboards and reports provided by the content package .
2 - The rules do not work for the administrator
3 - The rules do not work on your desktop or in groups
4 - if you publish a new pbi file on top of this current , the rules will be deleted. Update preference data using gateway.
I am the disposal for further information.
#PowerBI Seeking Leadership
Brazilian hug
IF YOU ARE RIGHT, MARK AS ANSWER TO GUIDE TO OTHER
i use a table called region myself for this. two solutions:
1. use the RSL in service version (click elipsis on dataset then security). This is super easy but the RSL is still beta and will be overridden on data refresh.
2. use DAX function username() as a filter. This works if your table contains all your users ID's assigned to the correct regionalities. Then just join region[reagion_name] to fact[region_name] (or whatever it might be).
User | Count |
---|---|
141 | |
113 | |
104 | |
78 | |
64 |
User | Count |
---|---|
136 | |
125 | |
107 | |
70 | |
61 |