Forum Discussion
Direct Query for Power BI Datasets cannot display visuals for one of the datasets for App viewers
I don't think you guys are understanding my issue.
The problem is that I have reports connected to 2 power bi data sets ( Direct Query for Power BI Data Sets). My users have view access to the App. The visuals from 1 of the power bi datasets are not showing up in the service, but if I give them access to the workspace as memebers, then the visuals show up fine.
However, I don't want them to be members of the workspace. I just want them to have view access to the app.
I can confirm that this issue is very valid and is recently bothering us in a very similar setup.
Trying to rephrase the issue from my perspective, maybe someone has new ideas for a solution?
Published Power BI App uses two file sources: One direct query, one import.
As soon as fields from the direct query are used, the visuals show errors to the user (! In the published App, not in the Desktop version when I am working on the report)
The users experiencing these issues have build permission for
- the Power BI dataset of the App that contains the visuals that throw errors (see screenshot)
- the Power BI dataset that is connected to the App via DirectQuery.
The sensitivity level of both reports is Internal.
Note: I have duplicated the page shown above and linked the visuals to the exact same dataset from the DirectQuery, but via an Import. Result: The users can see the visuals that use the imported dataset. The users get errros for the page with the visuals connected to the DirectQuery dataset.
In short:
Database 1 -> (Import) -> Power BI Report A : User sees all visuals
Database 1 -> (Import) Power BI Report B -> (DirectQuery) -> Power BI Report A: User gets errors
-> I am struggling to understand what other permissions I could still grant users to make them be able to view the visuals again.
Any ideas?