@v-diye-msftI thought of it but I require my users to export the underlying data as well. Anyways I have followed the similar approach but replicated the entire table ( 3 tables in my case). Marking this comment as a solution.
@Greg_Deckler I dont think this will work when RLS is applied based on the userprincipalaname. So basically the users can see the data based on their logins or heirarchy. However I want to bypass this RLS which is based on username only for two tabs and allow every user to see all data in these two tabs.
I have users 'a' 'b' and 'c'.
Tab 1 to 4 -> user 'a' can see only data relevant to 'a'. and so on for other users too.
Tab 5 and 6 -> user 'a' can see all data including that of 'b' and 'c' and so on for the other users as well.
@deepakramamurth Right, so the thought is to duplicate your fact table data and not have it connected to whatever table your RLS is tied to. But would need to better understand your model and data to see if it would work.
Typically the way I have worked around this issue is creating a summarization table within the model. This table is disconnected from any tables that have RLS applied. By doing this, users can see summarized data but not the underlying data that comprises those aggregations.
Community Support Team _ Dina Ye If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.