Forum Discussion
Implement RLS through an Import-Mode Table onto a Published and Connected Semantic Model
Hi Knegge ,
Apologies for the late answer, and also apologies for this late explanation but my first focus was the RLS and although you have gave a good print-screen and explanation on the way you picked up the tables I did some "selected reading".
When we have a composite model the tables that are not within the same type or location when the relationship is created they have a weak realationship that is why you have a break icon near your tables on your screenshoot.
Adding to this and much more important is that the RLS is only supported for Import and Direct Query not simultaneos, and when you refer to Live connections to Analysis services, your case then this needs to be handle in the on-premises model.
You can also check this video with an explanation on how this limitations work and why
Overall the short answer is that for the RLS to work you need to do it in the semantic model you have and not on the Direct Query one since it's connected to analysis services.
Hi Knegge ,
I'm looking into your relationships and you have a one to one from the RLS to a Business hierarchy is this table a dimension table or a fact table? How does the Business hierarchy relates to the rest of the model?
Also can you share what is the formula that you are using in the RLS and in what field you are applying the DAX for the RLS.
Hi Miguel,
The Business Hierarchy Table is the shared Dimension Table for some fact tables.
The DAX for the RLS is "CONTAINSSTRING('Profit Center RLS'[email_array],USERPRINCIPALNAME())" since the Mails are in an array.
In a seperate model that has all tables as import mode from DBX this filtering through the 1:1 RLS to BH works without fail.
For this specific case it is nessecary that I apply the RLS thorugh a new imported table from DBX to a published Semantic Model that doesnt have RLS on it yet.Hi Knegge,
Thank you for reaching out to Microsoft Fabric Community.
Thank you MFelix for the prompt response.
Thank you for the response and additional details.
The DAX expression itself looks fine. Looks like the main issue here is related to the model architecture and current composite model limitations rather than the RLS formula. Please follow below steps:
Please try to implement the RLS directly inside the original semantic model itself:
- Add the Profit Center RLS table into the original semantic model
- Create the relationship there and define the RLS role in that semantic model
- And then republish it.
Thanks and regards,
Anjan Kumar Chippa
Hi Knegge ,
Apologies for the late answer, and also apologies for this late explanation but my first focus was the RLS and although you have gave a good print-screen and explanation on the way you picked up the tables I did some "selected reading".
When we have a composite model the tables that are not within the same type or location when the relationship is created they have a weak realationship that is why you have a break icon near your tables on your screenshoot.
Adding to this and much more important is that the RLS is only supported for Import and Direct Query not simultaneos, and when you refer to Live connections to Analysis services, your case then this needs to be handle in the on-premises model.
You can also check this video with an explanation on how this limitations work and why
Overall the short answer is that for the RLS to work you need to do it in the semantic model you have and not on the Direct Query one since it's connected to analysis services.
