Forum Discussion
Responsive ResidentAnalyze in Excel Error
Hey AUaero ,
I posted that original thread. Nobody was forthcoming with a useful answer, but I did get to a solution.
Wait for it... it's a bit of a crazy fix.
So, I found that it depends how you create your Analysis Services connection when you first create your Power BI report.
If, when you use the Get Data wizard, you specify the database in the first dialogue screen, then the report works fine when you build it, but once published the Analyze in Excel gets the error you've described.
If however, rather than specify the database, you click through the dialogue screen and select the database, and then the model you wish to connect to, the PBI report seems to understand the metadata needed for the Analyze in Excel capability to work.
So... don't do this:
Do, do this:
Let me know if this helps, or whether this is just some quirk that seems to have helped us.
Memorable Member
Responsive ResidentThanks, venal. I had already reviewed that thread and didn't find a solution there. My account has full privileges on the SSAS server, so I don't believe it is an issue where the user isn't privileged to view the SSAS model. I also checked to ensure that the Analyze in Excel feature was not blocked administratively (it is not).
I can use Excel to successfully connect to the SSAS model in question. It's only when I try to access the ODC file generated by Power BI that I get the error message.
Hey AUaero ,
I posted that original thread. Nobody was forthcoming with a useful answer, but I did get to a solution.
Wait for it... it's a bit of a crazy fix.
So, I found that it depends how you create your Analysis Services connection when you first create your Power BI report.
If, when you use the Get Data wizard, you specify the database in the first dialogue screen, then the report works fine when you build it, but once published the Analyze in Excel gets the error you've described.
If however, rather than specify the database, you click through the dialogue screen and select the database, and then the model you wish to connect to, the PBI report seems to understand the metadata needed for the Analyze in Excel capability to work.
So... don't do this:
Do, do this:
Let me know if this helps, or whether this is just some quirk that seems to have helped us.
- AUaero
j0hnnyw1nter that absolutely worked. I probably wouldn't have stumbled upon that on my own, so thanks!
This sounds like a bug to me.