Forum Discussion
Username() filtering a simple table. No RLS or TABLE EDITOR
What you are doing is basically dynamic RLS. Note that USERPRINCIPALNAME() is preferred. USERNAME is inconsistent between desktop and service.
- Veigale2 years agoFrequent Visitor
yes, I will use USERPRINCIPALNAME().
I wouldn't want to enter users into the security configuration on the service. there are 800 employees.
I already tested and managed to get the nickname through the measurement, but I couldn't put it in a data segmenter, for example.I'm a newbie and I believe there must be a maneuver for this dynamic rls.
- lbendlin2 years agoSuper User
Read the documentation. Dynamic RLS works by having a reference table with email addresses and their permissions. That is your RLS table that then needs to control the rest of the data model.
- Veigale2 years agoFrequent Visitor
See, I checked some dynamic RSL guidance, but see. In this step I have to enter the 800 employees' emails, for example.
And this is also dynamic. Tomorrow it could be 700/900.It's just something so I don't have to do this that I'm looking for.
See the figure.
I am required to enter emails for RLS to work.
- Veigale2 years agoFrequent Visitor
I'm going to delve deeper into RLS.
But in the service, don't I have to insert the users that are in the table?That would be the difficulty.
If maintenance on the service is not necessary, the problem would be solved with the internal table.