Forum Discussion
Close and Restart Power BI Desktop

This bug has been around for a few months now. I reported it with 'send a frown' (twice) but it's still persisting.
If I remember rightly it coincided with the use of 'Quick Measures' when they were first released. However I've recently found that using TREATAS({}) has triggered it too.
One of my desktop files is completely stuck in this state and I began having the same problem in another after having a break waiting for the June update (in the hope there was a fix...) as mentioned when trying to use TREATAS.
The entire model seems to become inaccessable; you can't view any of the tables (they all become empty), refreshing brings back a server connection error and you can't view any of the measure/calculated column formulas.
Even DAX Studio doesn't detect a model schema and you cannot connect this way at all.
I'm afraid the issue seems to be persisting and as I don't know what's causing it I can't avoid/work around it!
It's causing a lot of disruption to our development and management aren't entirely convinced to begin with.
Surely can't be the only person to have experienced this?
10 Replies
- vanessafvg
Community Champion
CJ1608 as a work around maybe rewrite the measures without quick measures?
- CJ1608
Advocate I
I haven't used them since and still getting the issue. Even with them turned off.
As I said, even TREATAS() triggered it recently. I've had it happen for other reasons but I can't remember the exact details anymore.
- vanessafvg
Community Champion
CJ1608 have you got enough memory? need more information to understand, have you looked in the diagnostic logs? i.e options and settings / options / diagnostics / enable tracing
- AnonymousNot applicable
Hi , I am experiencing similar issues.
When we have a SSAS Tabular model as source (SQL Server 2016 SP1) and you add a quick measure in the Power BI Desktop file then then it seems to break the Tabular. I need to redeploy the Tabular model and the PBIX file cannot be open again.
This is posing a challenge as the Power users want to add their own measures as part off the Self Serviec capabilties off Power BI.
Would a Cumulative Update of SQL Server 2016 SP1 maybe fix the issue?
Kind Regards, Drickus