Forum Discussion
Semantic Model with direct query permissions
- 1 year ago
You definately need build permission, I ran into this problem a while ago and got confirmation from Microsoft.
I think the suggestion is to daisy chain DQ over AS models to together
Import -> DQ1 -> DQ2
You would grant build permission on the DQ1 model but not the import one. DQ1 would have a subset of the tables
Thank you, Deku , for your response.
Hi Giu,
We sincerely appreciate your inquiry on the Microsoft Fabric Community Forum.
In addition to the response provided by Deku , please consider the following alternative method, which may help resolve the issue:
Instead of sharing the entire semantic model, create a new dataset that includes only the tables required by the other department.
- In Power BI Desktop, create a new dataset by connecting it to the primary semantic model (A).
- Select only the tables necessary for the other department.
- Publish the new dataset to a dedicated workspace and share it with the respective department.
If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members encountering similar queries.
Thank you.
- Giu1 year agoFrequent Visitor
Hi v-pnaroju-msft,
This is exactly what I have done.
My concerns are:
- We do not want to refresh different semantic models at different times.
- To build a new report from semantic model B, I need to grant the Build permission on the main semantic model. However, based on the documentation, it seems that Read permission alone should be sufficient: https://learn.microsoft.com/en-us/power-bi/connect-data/service-datasets-permissions
ThanksKind RegadsGiuseppe- Deku1 year ago
Super User
You definately need build permission, I ran into this problem a while ago and got confirmation from Microsoft.
I think the suggestion is to daisy chain DQ over AS models to together
Import -> DQ1 -> DQ2
You would grant build permission on the DQ1 model but not the import one. DQ1 would have a subset of the tables