Forum Discussion
Cannot connect to Power BI dataset
- Anonymous6 years ago
Anonymous So we ended up taking a look at it with my network colleague and we've come to the conclusion that Power BI started to ask for MSSQL and https requests which couldn't get through our proxy. It's strange because we haven't done any changes related to that so probably something had to have changed on MS side. I couldn't find anything in the updates or Power BI blog so I can be wrong of course. Thanks for the help again!
Hi Anonymous ,
it's the same in a shared workspace and in my own as well. I'm an admin in the shared workspace as well and it happened with multiple (two to be exact) workspaces where I am an admin at.
When I download a simple file from a workspace it works.
The problem occurs when I trying to create a new file and connect to a dataset from the Service and when I open an already created report from my directory which has a datasource from a Power BI dataset.
(I created a workspace and there is currently two reports/files in it built on to the same dataset - the master is OK and working but the one I created on to the masters' dataset has this problem)
Hi Anonymous ,
so on one hand I just updated the latest version of Power BI desktop and it's still the same. On the other hand, I tested it with two other colleagues and it's the same for them as well. Can it be linked to some IT-network security issues or such?
- Anonymous6 years agoNot applicable
Anonymous This is an odd one, as I think it should work. Are your workspaces v1 or v2? That matters more with the shared datasets, and share datasets across workspaces (tenant setting), but just connecting to a different source should work. If it is just a simple connection... you may need to contact support as this doesn't add up for me.
- Anonymous6 years agoNot applicable
Anonymous ,
thank you I will do so. Could you please help me with the v1, v2 workspace question because I'm not familiar with what it should refer to.
Thanks again!
- Anonymous6 years agoNot applicable
Anonymous v1 workspaces are tied to O365 groups, so when you create one you create a universal group. This caused a bunch of mayhem in an org for obvious reasons. The new v2 workspace (which you can enable in admin portal - tenant settings) breaks that tie and allows you to create workspaces that are Power BI specific only. You can link OneDrive folders to them, but inherently they don't have one. There is a bunch of new functionality (shared datasets across workspaces being one) that require a v2 workspace.