March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Apologies if this is confusing...
I have a "core" semantic model called "Financial Model". It has RLS implemented within it. It works fine when tested within Power BI Desktop and also works with a very basic "RLS Test" report on the Power BI service. However, I have another report called "Expense Report" that is also built on top of the "Financial Model" model and RLS does not work within it.
My theory is that because "Expense Report" has some custom measures, when published, a new "intermediary" model called "Expense Report" is published alongside it and RLS is not being passed from the "Financial Model" model, up through to the "Expense Report" model, and ultimately to the "Expense Report" report. Hopefully the image below helps.
Can this be fixed? In other words, can I have a report with custom measures, built on a model with RLS, and still have RLS passed through to my report?
Solved! Go to Solution.
I got to the bottom of this. At some point, one of the developers enabled DirectQuery, which creates this "intermediary" semantic model. I don't think there's a way to remove that so we are copying and pasting everything from the original report to the new report.
I got to the bottom of this. At some point, one of the developers enabled DirectQuery, which creates this "intermediary" semantic model. I don't think there's a way to remove that so we are copying and pasting everything from the original report to the new report.
Hi @delish68
The RLS is only applied to its semantic model, it cannt be carried on to the semantic model that is built on top of it.
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
There isn't a semantic model explicitly/intentionally being created on top of it. I'm only guessing that it's being created because the report has some custom columns or measures in it. The intention is for the report to sit directly on top of the semantic model with RLS. Is there a way to resolve this?
You can build a new report with live connection to your dataset
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
That's exactly what we did. However, when we publish the report, we end up with an additional semantic model with the same name as the report (which points to the live Power BI dataset).
Sorry, you need to create it in the service
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
It's a complex report that's already been created. Having to create it in the service seems like an odd requirement. I think the important question is, why is this additional semantic model (Expense Report model) being created when my report is built on the "Financial Model" model?
Because you have created it when using Get Data in power bi desktop.
The main purpose for that action is when a developper creates a big Dataset or, Dataflows or Datamart to be reused by other users without editing the master one for security reasons.
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
I have created other reports in Power BI desktop, based on the Financial Model (using Get Data), and it does not have the same behavior of creating an additional model when publishing.
Not same behavior ! and after publishing you don't get a new Semantic model in the service !
Sorry but It seems weird.
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
36 | |
26 | |
19 | |
11 | |
8 |
User | Count |
---|---|
54 | |
43 | |
24 | |
13 | |
12 |