Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more

Reply
Miguel_Rojo
Advocate I
Advocate I

Build Access - Direct Query report

Hi community!

 

I have three questions reggarding "Building Access" in one specific scenario.

I proceed to list the contexts, hope you can orient me:

 

Scenario 1: Build Access - Report created using Direct Query 

  • I have a report published in my Workspace
  • This report uses a "Direct Query" connectin

Question 1: In that scenario, Can I provide "build access" to other users that are not part of my workspace the same way it would if the report had been created using an "Import" connection?, Or we can not create reports based on reprots that use a "Direct Query" connection?

 

Question 2: Once I've provided "Build Access", all the reports they create based on my "Parent Report"  will be visible to they're audience? (even if their reports are in a different Workspace)

I mean, the users of "their Child Report" won't need access to my "Parent report" to succssfully see their data?

 

Question 3:  Is there any limitation to the fact that the "Parent Report" has a "Direct Query" connection?

 

Any comment will be highly appreciated!!

1 ACCEPTED SOLUTION
BA_Pete
Super User
Super User

Hi @Miguel_Rojo 

 

-1- Yes, you should be able to assign Build permissions to the model in the same way. However, based on the nature of Direct Query connections (all visual queries are sent directly to the source), be mindful that anything your new 'Builder' creates will increase load on the source so ensure they know/understand this to avoid undue load on your source.

-2- No, reports they create won't necessarily be visible to their audience by default. They will still need to share their creations appropriately. No, their audience will not need access to your parent report to view the child report, but they will inherently be given a level of model access that allows them to view the child report content.

-3- Yes, many limitations, from restricted M and DAX functions to potentially excessive source load. Have a read through the following for a good overview:

https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about 

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




View solution in original post

2 REPLIES 2
BA_Pete
Super User
Super User

Hi @Miguel_Rojo 

 

-1- Yes, you should be able to assign Build permissions to the model in the same way. However, based on the nature of Direct Query connections (all visual queries are sent directly to the source), be mindful that anything your new 'Builder' creates will increase load on the source so ensure they know/understand this to avoid undue load on your source.

-2- No, reports they create won't necessarily be visible to their audience by default. They will still need to share their creations appropriately. No, their audience will not need access to your parent report to view the child report, but they will inherently be given a level of model access that allows them to view the child report content.

-3- Yes, many limitations, from restricted M and DAX functions to potentially excessive source load. Have a read through the following for a good overview:

https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about 

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




Thanks for the detail answer @BA_Pete 

 

Have an amazing day,

Miguel

Helpful resources

Announcements
Notebook Gallery Carousel1

NEW! Community Notebooks Gallery

Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.

April2025 Carousel

Fabric Community Update - April 2025

Find out what's new and trending in the Fabric community.