Edit Tables in Directlake Model - We could not fetch your warehouse schema

[joeparkinson]

I've got a semantic model based on a warehouse. Its not the default semantic model, as i've used tabular to add field parameters so didnt want to muck up the default model.

I've now got new tables in my warehouse, and want to add them to my semantic model. When clicking edit tables, I get the error "We could not fetch your warehouse schema". Could this be because i've edited the model in tabular? If so, is there another way to edit the tables in the model?

[Lambanlaa]

I am having this issue too 

[RubyM]

I have a potential workaround but requires using SSMS and knowing a bit of XMLA.  I added a new column to my view for my semantic model which is join to the Fabric warehouse and got that error when I tried to edit tables.  Following the instructions on this website I had to manually add the column to my view (removing the lineagetage and sourceLineageTag fields).  Processed the table and refresh and I see my column now.

However, I am still getting that error if I click on the Edit table in my semantic model but at least I am able to see my new column now.

[v-cboorla-msft]

Hi @joeparkinson 

Following up to see whether you got any insights on your query or just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thanks.

[JayJay11]

We on our side have an open ticket on the issue #2404050050000081.

Hope it will be resolved soon 🙂

[joeparkinson]

My solution has been to stop using warehouses to be honest, i'm just going to use lakehouses and maintain relationships in a semantic model.

[RubyM]

I'm getting this exact error as well.  Added a new semantic model to a warehouse and had to change one of my tables.  Clicking on the "Edit tables" in new semantic model and getting:

We could not fetch your warehouse schema

An internal error occurred.
Please try again later or contact support. If you contact support, please provide these details

[v-cboorla-msft]

Hi @joeparkinson 

Thanks for using Microsoft Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.

Appreciate your patience.

Thanks

[JayJay11]

Hello @v-cboorla-msft can you please let us know the status on this? It is now a while since this reply.

This issue is still not resolved. We have an open ticket #2404050050000081 with Microsoft support since weeks, but this has not been helpful at all so far. The ticket is I think passed around between teams and I have a feeling that no actual Microsoft employee / engineer has looked at the issue.

Also tagging @cpwebb I saw you were commenting on the topic of field parameters in direct lake semantic models in another thread. Maybe you can help or give more context, not sure. When adding a field parameter table with Tabular to a Direct Lake semantic model (using XMLA / Tabular Editor 3), one cannot use the functionality "Edit Tables" anymore in the semantic model in the service.

Any help here is highly appreciated, thanks!

[cpwebb]

I believe the situation with field parameters is the same as with calculation groups (see https://powerbi.microsoft.com/en-us/blog/announcing-calculation-groups-for-direct-lake-datasets/) in that if you add a field parameter to a Direct Lake model using Tabular Editor you can no longer use the Web Editor to make changes to the model.

[JayJay11]

Opening the data model with the web editor still works as well as any other changes that I can do, e.g. creating a measure, EXCEPT the "Edit Tables" functionality. I honestly think this is unintended from Microsoft side, i.e. a "bug". However, I don't know how I can reach someone at Microsoft that can take this up and have a serious look at it.

At the same time Microsoft support (MINDTREE) tries to close our ticket because the claim the error is caused by Tabular Editor, which is not actually true, it is caused because using a field parameter table in DirectLake. There is no official documentation that states that field parameters are not supported in Direct Lake. I understand that calculated columns as well as calculated tables derived from existing DirectLake tables are not supported. However, a field parameter table is a 'standalone' table and not derived from an existing table (right?).

I think I refuse to close this ticket until someone at Microsoft actually looked at it.

[cpwebb]

I have brought this to the attention of the PM in charge of the Web Editor and will let you know what I hear back.

[JayJay11]

Hi @cpwebb - can I follow-up if there is a feedback yet? Thanks!

[JayJay11]

Same issue here @v-cboorla-msft , please let us know the status. Thanks!

[JayJay11]

I think I can confirm that the issue is there as long as there are field parameter tables in the model. I deployed a copy of the model via XMLA and deleted the parameter tables and the "Edit tables" functionality works again.

However field parameter tables have become crucial to us so a fix of this issue will be highly appreciated.

[Ramakoti]

Hi @v-cboorla-msft 

I'm facing the same issue, Please let me know if we have solution for the same.