Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Idrissshatila

Power Bi failed to open, Unsupported Table name " Measures" has been found in model schema

Submitted by Super User on ‎02-24-2025 11:55 PM

Hello Team,

 

I noticed many users faced this error "Unsupported Table name " Measures" has been found in model schema" after

 

the Power BI February update, it has some new validation that will prevent opening your pbix files if you've previously created a table named " Measures" with the space in front (using [ Measures]=  )

 

error.png

 

one current solution found by Stephanie Bruno is that: To solve this, you'll have to download an older version of desktop (I used November), open your pbix file and rename the table, and save. Then you'll be able to open it in the latest version again.
You can get older versions here: https://lnkd.in/enrn8cQZ 

 

link to Her post on linkedin: https://www.linkedin.com/posts/brunostephanie_previous-monthly-updates-to-power-bi-desktop-activity-... 

 

Status: Investigating
See more ideas labeled with:
10 Comments (10 New)
Comments
ebeery
Memorable Member
Memorable Member
‎02-25-2025 03:19 AM
We noticed this issue and opened a support ticket yesterday. Unfortunately, the only "workaround" proposed by Microsoft so far has been to revert back to the November version. I'm very hesitant to apply the table rename "fix" on models which have downstream dependencies, since it will mean many broken reports and visuals.
AmboyOz
Regular Visitor
‎02-25-2025 09:19 PM
I started getting the same issue. The Jan-2025 version works but it took a while to find and download old versions.
Anonymous
Not applicable
‎02-25-2025 09:47 PM

Hi all,

 

Yes, there is no clear solution about this issue yet. PG team suggests users to roll back to previous November version first, sorry for the inconvenience.

 

Best Regards,
Community Support Team _ Caitlyn

Anonymous
Not applicable
‎02-26-2025 04:02 PM
Hi All, I'm experiencing the same issue, but don't have the ability to roll back to an earlier version since updates are controlled by our Software Center app. I'm currently dead in the water. Is there an eta for a fix? Thanks! Jim Hancock T-Mobile
chandukokku
New Member
‎02-26-2025 06:43 PM
Faced the same issue and the only method that has worked is Roll out to the Older version preferably NOV 24 which I did today after uninstalling Feb25 version. Uncheck Auto Update and make sure you change the table "Measures" to any other name and you are good to go.
ErikT
New Member
‎02-27-2025 05:28 AM
@chandukokku Where did you find the older version installer? Thank you, ErikT
ebeery
Memorable Member
Memorable Member
‎02-28-2025 12:27 PM
FYI, this appears to now be fixed, as of version 2.140.1205.0
vanessagg
Regular Visitor
‎03-19-2025 03:07 AM
when will this be resolved for the latest version? most company's manage the installation of power bi desktop on peoples machines, and going back to an older version is painful. the latest version needs to have this fixed and currently its throwing an issue in feb version. Will it be fixed in march?
Bron_Smith
Frequent Visitor
‎03-24-2025 04:48 AM

I'm on version 2.140.1577 and STILL getting this error. Been getting it for ages and now literally can't move forward because I can't open a report to peer review it. I get asked to apply or discard changes on opening the report - apply removes every single datasource from the report. EVERY. SINGLE. ONE. Discard throws up the rename error, with only "report" or "cancel" as the options. If I cancel, I then can't refresh the report to check it. If I report, then the same thing. Going back to previous versions is not an option as its managed by Corporate and the latest versions are pushed to our machines. Can't wait another quarter!!!

 

To add: This has been going on for more than a few months. The problem started for me before the November release

 

Edited 2025/04/02 Version Rollback is NOT an option. The Organisation I'm with will not consider this.

Bron_Smith
Frequent Visitor
‎04-17-2025 01:13 AM
After much negotiation with our IT department, I've rolled back to November 2024, but the error persists. Its really getting old now. Also, the solution offered to open the pbix, rename the tables and save and then open in the new version is going to take me all year - I have 8 departments and heaven knows how many workspaces to go through!! Feedback Type: Frown (Error) Timestamp: 2025-04-17T08:08:14.5471245Z Local Time: 2025-04-17T09:08:14.5471245+01:00 Session ID: 2fd824b3-29a2-49c3-891a-faa8b790ed14 Release: November 2024 Product Version: 2.138.1452.0 (24.11) (x64) OS Version: Microsoft Windows NT 10.0.19045.0 (x64 en-US) CLR Version: 4.8 or later [Release Number = 528372] Peak Virtual Memory: 72 GB Private Memory: 1.01 GB Peak Working Set: 0.981 GB IE Version: 11.3636.19041.0
Idea Statuses