This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi All,
I have an issue where a single user, out of ~80 that have access, can't see all the data in any report that uses Analysis Server as the data source. They can see all data in all reports where the data is imported straight into PowerBI.
This user has access to the Workspace these reports reside, confirmed by the fact they can see data in reports where data is imported into report.
In AS, Roles and Persmissions have been set up so a "Read and Process" permission level has been assigned to "Everyone'.
I've checked with IT re their permissions and user groups, and they're the same as others.
I had this issue once before with someone else, but it corrected itself after a while and he could all of a sudden access the data. The person who is currently having the issue has had it the entire time.
I'm thinking it's a back end user permissions thing but everything seems normal.
AS Roles
Error Message in PowerBI (Online)
Solved! Go to Solution.
Hi All.
We resolved this issue so I thought i'd update this post.
Solution: The issue was that this particular person's UPN didn't match their username. Their username/email was Name@xyz.com.au and their UPN was Name@xyz.local. I don't know why IT had it set up like that. To solve this issue, you could go to each gateway in PowerBI Online and map the user's com.au to their UPN .local OR, change their UPN to match their username (email). I ended up getting IT to change his UPN to match his username so I didn't have to apply it to every model we have and every new model we created going forwards.
History: I ended up contacting Microsoft. I supplied them diagnostic logs and when I tried to run a script they supplied that required the user's UPN, it errorored out using Name@xyz.com.au. I asked IT what his UPN is and it turned out it was .local. The script worked when using .local as that was their UPN. We mapped Name@xyz.com.au to Name@xyz.local in PowerBI Online Gateway settings for one of the Gateways and the user was then able to access the report using that Gateway. That's how we confirmed that the issue was his UPN not matching his username. He was the only person in the company with a UPN of .local, hence why he was the only person who couldn't access reports using AS models that had the usergroup "Everyone" in the persmission settings. It must user their email to grant access to the model.
Hi All.
We resolved this issue so I thought i'd update this post.
Solution: The issue was that this particular person's UPN didn't match their username. Their username/email was Name@xyz.com.au and their UPN was Name@xyz.local. I don't know why IT had it set up like that. To solve this issue, you could go to each gateway in PowerBI Online and map the user's com.au to their UPN .local OR, change their UPN to match their username (email). I ended up getting IT to change his UPN to match his username so I didn't have to apply it to every model we have and every new model we created going forwards.
History: I ended up contacting Microsoft. I supplied them diagnostic logs and when I tried to run a script they supplied that required the user's UPN, it errorored out using Name@xyz.com.au. I asked IT what his UPN is and it turned out it was .local. The script worked when using .local as that was their UPN. We mapped Name@xyz.com.au to Name@xyz.local in PowerBI Online Gateway settings for one of the Gateways and the user was then able to access the report using that Gateway. That's how we confirmed that the issue was his UPN not matching his username. He was the only person in the company with a UPN of .local, hence why he was the only person who couldn't access reports using AS models that had the usergroup "Everyone" in the persmission settings. It must user their email to grant access to the model.
@Erik_Debono
Generally the problem is caused by access permission, check whether you have include the user as the member in AS model.
If you have every settled, you should go to issues forum for some bugs like this.
Best regards
Paul Zheng
You could check the Issues forum here:
https://community.powerbi.com/t5/Issues/idb-p/Issues
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 28 | |
| 24 | |
| 22 | |
| 22 | |
| 18 |