Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Existing Desktops will not open after installing March update

After installing the March update, several of my desktops would no longer open.  I received this error "This model doesn't have a named expression named Measure" on these.  When building desktops, I use the "Enter Data" option and create a folder called "Measure" and this is where I store all of my measures for the desktop.  I uninstalled Power BI and reinstalled the February update.  This did not fix the issue.  All of these desktops were working perfectly until today. It would be a disaster if I cannot get into these desktops.  HELP!

 

Measure Error.png

 

 

Status: New
Comments
v-qiuyu-msft
Community Support

Hi @Anonymous , 

 

Did you create a folder "Measure" like below? 

a3.PNG

 

Based on my test in Power BI desktop version 2.79.5768.721 64-bit (March 2020) follow your steps, it's able to close then reopen the report. Please run the same desktop version as ours then run it with administrator, click on File ->Open to open the report. 

 

Best Regards,
Qiuyun Yu

Anonymous
Not applicable

This is how I create measures (see below).  Also no clue how to run as an Administrator.

 

Measure Error 2.png

Anonymous
Not applicable

Sorry...that is how I create the measure folder.  Then I add measures into this has needed.

Anonymous
Not applicable

I ran into the same problem today with a file that worked fine two days ago. When opening a different file a message about 'metadata' was shown, which reminded me of the new preview feature that I may have switched on recently. I unchecked the feature 'Store datasets using enhanced metadata format', restarted the PowerBI Desktop and now my original pbix file could be opened.

 

enhanced metadata.JPG

 

After that I found out that one of my custom functions had 'Enable load' activated, which may (or may not) have been the true cause of this issue. Similar issue was reported here .