Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
We have a semantic model created that encompasses an entire business domain. There are various groups who need access to reports based on this model, and each one has differing RLS requirements that sometimes overlap subject areas within the model. Up until recently our path has been to create a copy of the base model and add the ACL table and RLS to the copy. This results in extra overhead in ensuring the two models remain in sync.
To try an minimize the overhead, I'm trying to create a new model using the original semantic model as a DQ source, and then adding the ACL table and RLS roles. However, I am running into a problem. It works fine in Desktop when using "View as role." The visual filters and displays as expected. When I publish it to a premium backed workspace, I cannot use the View as Role feature as I get the following error.
And when I have someone test who has permissions to the report and is added to the appropriate role they get this message.
Is there a setting in service I'm missing? Any other suggestions?
Please help!
Solved! Go to Solution.
Hi @Scott_BI
Unfortunately, what you are trying to achieve is currently a limitation in row level security. Here are more details Row-level security (RLS) with Power BI - Microsoft Fabric | Microsoft Learn
Hi @Scott_BI
Unfortunately, what you are trying to achieve is currently a limitation in row level security. Here are more details Row-level security (RLS) with Power BI - Microsoft Fabric | Microsoft Learn
For directquery model on power bi service.
you should use fixed identity
Learn how to specify a fixed identity for a Direct Lake semantic model in Power BI and Microsoft Fab...