Forum Discussion
Couldn’t retrieve the data for this visual
Hi Cody
Correct on both counts the problem sounds identical
1. Yes I have multiple connections, Google Analytics, PostgreSQL, Excel and CSV
2 Yes I have sent the dashboard to a team member and he has published it, shared it with me. He can view without a problem, I get 'couldn't load the data for the visual'. Consistant behaviour.
The error suggests 401 unauthorised access.
I have used chrome developer tools to view the http content, sent the HAR (http archive file) file to Microsoft.
As soon as I hear anything I will post the answer
Cheers
David
Hi David,
In my case, this turned out to be an oversight on my part...
I had gone poking around in the new Role Level Security in my Power BI Desktop file before publishing and created an empty 'New Role' which noone had access to.
Both add the users to the role in the dataset in the Power BI Service and removing / re-publishing the file has allowed sharing without issue.
May be you'll have the same simple fix - obviously a more descriptive error would have pointed me in the right direction!
Cheers,
Cody
- David4F10 years agoAdvocate I
Hi Cody,
Without looking I can only believe it is the same issue, I also have been interested in the new Role Level Security, the error suggests it authorisation issue.
Thank you for the direction, I will confirm the outcome.
Kind regards
David
- David4F10 years agoAdvocate I
Hi All,
This has been resolved, the issue was with "Role Level Security".
I created a role that restricted the report to only one county. I only had one individual in this role, but the report was not shared with him. Not sure this should have been an issue, but once the role was deleted the reports displayed correctly.
As the owner obtaining Quick insights was also affected by this, once the role was removed everything was happy.
Tread carefully with "Role Level Security"
Thanks Cody for pointing me in the correct direction.:smileyhappy:
Cheers
David
- codyj71010 years agoFrequent Visitor
Hi David,
Good to hear, obviously we're not alone working our way through the Role Level Security.
I suggested to Microsoft they enhance the related error message and it's been passed up to the product team.
Cheers,
Cody