Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
I have a report in powerBI service, for which I granted build access to 2 other users in the business to go and create their own visuals with.
They have created a new report but are now complaining that their users cannot see the visuals they have created using my dataset. They get an error "could not retrieve data". Their report uses directquery and they are saying that all their users also need to have build access to my dataset/report in order to see the visuals.
This seems like an enormous pita for me XD
Questions: is it really necessary to grant all their users build access or is there another way round? Are there any limits or considerations in having a great many users with build access? Should I be concerned about load?
Solved! Go to Solution.
Hi. It's true that users reading a report with live connection or direct query to other dataset can't see the visuals unless they have permissions to the source dataset. However, the build it's not necessary. You can just add them to the dataset unchecking all the boxes like "build", "reshare", etc. Just read. That should be enough for the users for reading the new reports created by the developers.
I hope that helps,
Happy to help!
If you build a report on top of a dataset in another workspace, whoever should view that report needs to have access to that dataset either via "viewer" in the workspace or via direct access to the dataset itself.
Build goes on top of the direct access and is not required.
Hi @dapperscavenger ,
Just to confirm that I understand completly the idea on this scenario, Is it correct my interpretation?
Question 1: The reason of this error was that the "Parent Report" was built using "Direct Query" method? (in other words, if the "Parent Report" would have been created using "Import" the Stakeholders of "Child Report" wouldn't have had the problems mentioned aboce?
Quesiton 2: ¿Siempre que se construye un "Informe infantil" basado en un "Informe de padres" que fue construido usando "Consulta directa", los usuarios del "Informe infantil" necesitan "Ver acceso" al "Informe de padres"?
I would really appreciate your comments,
Thanks!
If you build a report on top of a dataset in another workspace, whoever should view that report needs to have access to that dataset either via "viewer" in the workspace or via direct access to the dataset itself.
Build goes on top of the direct access and is not required.
Hi. It's true that users reading a report with live connection or direct query to other dataset can't see the visuals unless they have permissions to the source dataset. However, the build it's not necessary. You can just add them to the dataset unchecking all the boxes like "build", "reshare", etc. Just read. That should be enough for the users for reading the new reports created by the developers.
I hope that helps,
Happy to help!
Hi @ibarrau,
Just to confirm that I understand completly the idea on this scenario, Is it correct my interpretation?
Question 1: The reason of this error was that the "Parent Report" was built using "Direct Query" method? (in other words, if the "Parent Report" would have been created using "Import" the Stakeholders of "Child Report" wouldn't have had the problems mentioned aboce?
Quesiton 2: ¿Siempre que se construye un "Informe infantil" basado en un "Informe de padres" que fue construido usando "Consulta directa", los usuarios del "Informe infantil" necesitan "Ver acceso" al "Informe de padres"?
I would really appreciate your comments,
Thanks!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
50 | |
31 | |
26 | |
26 | |
25 |
User | Count |
---|---|
60 | |
49 | |
29 | |
24 | |
23 |