Forum Discussion
Error Message - Unexpected error encountered when opening report in Power BI Desktop
- Anonymous9 years ago
Mine is the same, so we could be onto a winner here. I will sometimes get an error on tabs without the matrix visual too, but only in report files where i've used it.
I might make a test file where i remove this visual and see if it fixes it.
- Anonymous9 years ago
Nope that didn't fix it. I've now gone to a tab, removed every visual and done a Save/Close. Going to this tab has not spawned an error. So i'll try removing visuals 1 at a time until i find it.
- Anonymous9 years ago
Are you by any chance using a custom visual "Hierarchy Slicer"? My error seemed to go away on the tab where i removed that visual.
Hi Ross,
I am facing the exact same issue.
Initially my reports were built using Matrix Visuals which were in Preview Feature. Post July updates. I have incorporated few more tabs in the existing report, which contains the Matrix Visual.
It was working all fine. Since yesterday, am getting the error everytime I open the report. Once I click on Close . The report works fine.
When I publish it to app.power bi, i do not get any error.
However, the users who will be using this report wants to access the report from Power BI Desktop.
So am trying to figure out a way to solve the issue.
Mine is the same, so we could be onto a winner here. I will sometimes get an error on tabs without the matrix visual too, but only in report files where i've used it.
I might make a test file where i remove this visual and see if it fixes it.
- Anonymous9 years agoNot applicable
Nope that didn't fix it. I've now gone to a tab, removed every visual and done a Save/Close. Going to this tab has not spawned an error. So i'll try removing visuals 1 at a time until i find it.
- Anonymous9 years agoNot applicable
Are you by any chance using a custom visual "Hierarchy Slicer"? My error seemed to go away on the tab where i removed that visual.
- Anonymous9 years agoNot applicable
Hi Ross,
Thank you for your suggestion.
I removed Hierarchy Slicer and the issue does not exist any more. I think, the slicer is probably triggering the issue.
Somehow that slicer is one of the requirement, we cant remove.
I have raised a ticket with microsoft. If I hear back from them with any resolution. I shall update the same to you as well.