Forum Discussion
Filtering data in Edit Queries not the same as using slicer
Hi Anonymous
Your requirement is to let users see data which they have pemission to, for example, user A can see data about user A, but can't see data about others.
If you are in this scenario, you could consider setting RLS on the report, thus dataset is limited to users.
Reference:
https://docs.microsoft.com/en-us/power-bi/service-admin-rls
additionaly, if my understanding and suggestion are not right, could you tell me how did you do the following?
specifically stated the client code on the customer table
Best Regards
Maggie
Hi Anonymous
Your requirement is to let users see data which they have pemission to, for example, user A can see data about user A, but can't see data about others.
If you are in this scenario, you could consider setting RLS on the report, thus dataset is limited to users.
Reference:
https://docs.microsoft.com/en-us/power-bi/service-admin-rls
additionaly, if my understanding and suggestion are not right, could you tell me how did you do the following?
specifically stated the client code on the customer table
Best Regards
Maggie
Thankyou
This will work for us.
RE: specifically stated the client code on the customer table
I specifically went into "Edit Queries" in power BI Desktop, added a filter on the customer table to the specific customer I wanted.
This meant the customer table only held a single row. (the rest were filtered out)
However, my related Orders table still had all customers in it, dispite the integrity rule on the relationship.
Now, i could go to that table and filter it also, to get the result i need, But that really starts to get messy going forward.
Row based security does work much cleaner.
I am curious why the relationship rule was not followed however.