Exception while parsing CSDL to create Conceptual Schema

[Anonymous]

Hey there,

Can anyone help me with this particular error message?:

For starters, It's a model built in Power BI Desktop and -I think- nothing has changed since yesterday when the report was loading just fine.

I've tried publishing it in different workspaces and removing the relationships to see if any of those may be the underlying problem, but seems a bit more complicated than that.

Thanks in advance!

[UtisDTI]

it 2025 and I´ve got the same problem.....
working yesterday and not working today.

An error occured creating a table from this datasource.
One or more errors occurred while converting CSDL to a conceptual schema.
Timestamp: 2025-07-04T14:34:11.555Z
Root activity ID: e91d278e-a251-6655-8555-b978ab5d8f34
Session ID: 00000bf46bb748c69b256aa170bec11a
Tenant ID: undefined
Cluster: https://wabi-west-europe-e-primary-redirect.analysis.windows.net/
Report ID: null
Capacity ID: undefined
ReportViewerVersion: 2025.6.4.1852

[adamant]

In our case this generic error "...failed to parse CSDL...' was caused by one of the measures being incorrectly written.

x_Is_Workday =  //IF ([Is Workday for Country] = TRUE(), TRUE(), FALSE())

Notice part of the statement was commented out. This was put in several months ago, but started manifesting itself only a few days ago. Dataset could be refreshed in the desktop PowerBI, but when we pushed it online and tried to refresh there it would be failing with the " Failed to parse CSDL..." error.  We tracked it down but gradually removing tables from the dataset, migrating the dataset and refreshing online. It took a long time but we finally found the problem in one of the measures.

[andymac]

I've had confirmation from Microsoft Support that this is a bug and the product team are working on a fix.  They sent me a link to this thread and suggested I remove calculation groups as a short term workaround!  Interestingly one of my clients dashboard, hosted in the US region has started working again this morning, another hosted in the UK region is still giving the same error.  No official ETA for a fix yet.

[MAFE62]

Just to tell you that the problem was solved in my case.... also hosted in US region.

Best regards!

[Anonymous · Accepted solution]

Yes! Mine's working too! 
Thanks for the update.

[Anonymous]

Thanks for the update!
Also, for those who use Analyze in Excel, that work for me without changing anything.

[FVINF]

The same issue has been reported in the "Issues" forum in the following link.

https://community.powerbi.com/t5/Issues/Exception-while-parsing-CSDL-to-create-Conceptual-Schema/idc...

A Community Support Team member has reacted to that post to ask for further information, so I have replied asking to use this post as further reference, since there is more information available here. It might be worthwhile to share your findings in that post, since it seems to be on the radar of the support team.

[tenfingers]

In my case, I was able to narrow it down to a KPI type calculation created with Tabular Editor. removing this fixed the issue:
Creating KPIs in Power BI Desktop - SQLBI

[Anonymous]

THANKS A LOT "tenfingers"!! 🙂
Did the same and now it works. 500+users are happy again. BR, Lars

[mookje77]

In my case, calculation group was the problem

[MAFE62]

This is what MS said about the problem:

"Thank you for time during our call today.
I wanted to provide an update on your case. Many users have reported the similar issue. This issue has been escalated and is currently being investigated by the product team.
For now we have everything we need from you. If additional logs are needed we will contact you. Also, we will keep you posted with any updates.
 
Thank you for your support and cooperation while working on this ticket."

[Anonymous]

Thanks for the update! It is clear that it is not something trivial, we'll just have to wait

[SIVNAPPA9774]

Same here... I deleted some measures and it works... Now I'm trying to discover wich measure is (there are a lot in my model and I know it is more than one)

[SIVNAPPA9774]

I found out which measures were giving error in the model and deleted them... After that I recreated theese measure and it is working now

[mookje77]

Which type of measure, please?

[SIVNAPPA9774]

Nothing special 😞   (one of then were just a subtration)... I noticed that were the last ones that I created.

I deleted some and tested, than deleted more and tested... until discover it

[alekos19]

Microsoft support told me that it could be an issue elated to powerbi version. Mine dates nov 21. Which are yours?

[Anonymous]

Tested both November 22 and October 22, none of those worked. 
In my case, deleting the calculation groups did the trick, but of course it's something I'm expecting to revert. At least it is a workaround..

[pschaer]

I have the same problem with a Dataset of a customer.

They have >2'000 Measures and there's a few Calculation Groups. 

No way I'm going to start troubleshooting which one is causing the issue...

@Microsoft: Please fix this ASAP!

[egakagoc2xi]

Same Issue