Forum Discussion
Filtering a semantic model for end-consumer
Have you considered the "App owns data" embedded scenario or RLS in general?
Yes we have, but for our scenario, I am not sure it can work.
Let's say we have 100 clients, and about 5 teams. We'd create RLS for the 5 teams, but that still means they get to see 20 clients each.
Do you think another approach would be to have 100 clients, each one having it's own O365 group. When adding users to the O365 groups, would they somehow only get to see the data for the specific client? Even when users are added to multiple O365 groups. For example user A would be added to O365 group 1, 2 and 3. Would user A still get to see all items from 1 to 3?
The final step for us, is connecting the data to Excel. So it's very important that user A only gets to see the data for item 1, when we deploy the Excel templates for item 1.
Read about the difference between static RLS and dynamic RLS. In your case a reference table in combination with USERPRINCIPALNAME may be more efficient.
I will look into that, thank you!
I checked the option for Dynamic RLS, but I am afraid it won't work for the scenario.
Say I have a O365 group per client, we have about 20 users. But the same user can be a part of multiple O365 groups. In the end this means that that user can still see all the clients he is connected to, instead of just one client per template we publish..