Fabric Can't edit an existing custom semantic model

[Airscape]

I am trying to edit an existing semantic model that is currently being used for a production dashboard. The edit is quite simple. I am just trying to add a new table. The table is valid exists in the same lakehouse as the model. I can query the table from the SQL endpoint.  I get the edit semantic model screen showing the already selected tables (32 of them). I add the new table and click confirm.  After about 2 minutes it fails with the message:

Activity ID: 0e155ef8-6ec3-4d35-b816-26d0d62b0d01
Request ID: d5ce5f99-97b6-4fbe-a118-e459d42ec5dc
Correlation ID: efabe48c-862c-eeff-ba1b-6a89a17324e1
Status code: 500
Time: Thu Aug 08 2024 16:59:06 GMT-0500 (Central Daylight Time)
Service version: 13.0.23827.61
Client version: 2407.4.20134-train
Cluster URI: https://wabi-us-central-a-primary-redirect.analysis.windows.net/

This has been going on for three days now.  I would be happy to submit a ticket but I cant do that as we do not have a premium subscription.  We are using F8 pay as you go.

Any help would be greatly appriciated.

[SEC-APAC-MB]

Hi everyone, I'm currently experiencing an issue with the Semantic Model that is preventing me from adding or removing tables. The specific error message is: {"error":{"code":"ExternalServiceFailed","pbi.error":{"code":"ExternalServiceFailed","parameters":{},"details":[{"code":"ModelingServiceError_Reason","detail":{"type":1,"value":"Error in ModelingEngineHost"}},{"code":"ModelingServiceError_Location","detail":{"type":1,"value":"ModelingEngineHost is failed"}},{"code":"ModelingServiceError_ExceptionType","detail":{"type":1,"value":"InvalidOperationException"}},{"code":"ModelingServiceError_Message","detail":{"type":1,"value":"There is no transaction in this session."}}}]}}} I am unable to resolve this myself, so please try again later or reach out to support for further assistance. If you do contact support, kindly provide them with these details. Thank you!

[frithjof_v]

I am also getting this error message "There is no transaction in this session".

However, when I tried again later (perhaps half an hour later), I didn't get the error and it worked.

[PunChili]

Dear all,

Update: going on with the tests resulted in the fact that even if the relationships does not have any issue anymore. I was not able to add a new table. This was only possible when deleting all relationships, adding the table and recreating all ofthe relationships again.

[PunChili]

hi,

we also have the same issue. Is the refresh of a custom semantic model depending on the default semantic model refresh? In our enviornment I can see that the refresh date is not aligned with the lakehouse / sql analytics endpoint refresh date --> default semantic model updated, still the same issue.

Btw: I received the same error message when deleting a table from the model. Happily it was deleted. Unfortunately I cannot add it again anymore... again the same error message.

Do someone of you use deployment pipelines? Because, the same model is working in th eoriginal workspace, but throws the issue in the new workspace where it is deployed to.

Is someone already in contact with support?

[Airscape]

The solution for us was a field that was not specified correctly in one of the table. Once it was found has worked since then.  Your second question do we use deployment pipelines. No we do not as they don't work with direct lake models.  Hopefully it is on the roadmap to get fixed at some point. The documentation specifically says they won't work.

[PunChili]

Hi Airscape, thx answereing me. What do you mean by "not specified correctly"? May I ask you to send me the link for the deployment pipelines limitations?

[PunChili]

...the issue was on the relationship.

[Airscape]

As SorenHou said this is not a relationship problem. First it is a terrible error message, gives you no information that is of any use.  My fix was because of a bad data definition for one column. I presume the SM you have used to work. If so I would look first at any tables you have added and check each column to make sure what is defined is actually what the data is. This fixed it for me.

[Airscape]

This problem has finally been solved. The error was on our side. A new field had been added and it was not done correctly. This caused the relationship to become invalid.  Yes it was our own doing but the error message was of no help what so ever.  Would have been nice if it at least said problem with x on table y.  The message we got was useless.

[SorenHou]

Hi Airscape

I had the samme issue, and could not find any solutions online. I had started to recreate my semantic model when I found the solution. 

In one of the relationships i had between two string values in two tables, one of the values were no longer a string but a long. I had properly changed it in the prepare step before without knowing. That created the error. 

If you go through all the columns you have in relationships and make sure they are the same data type, that migth fix your problem.

[Anonymous]

Hi @Airscape 

There are a few questions I would like to confirm with you:

1. Try again after refreshing the page and clearing the cache to see if the problem still exists.

2. Did you select tables in the "SQL analytics endpoint" to add to the existing semantic model?

Here's the two normal ways to add your tables to semantic models as follows:

• In Lakehouse workspace, open the SQL analytics endpoint. Right click the table to select “Add default semantic model”.

• In Lakehouse workspace, open the SQL analytics endpoint. Manually pick tables to be added to semantic model through “Manage default Power BI semantic model” in the ribbon bar.

3. Have you enabled the option "Sync the default Power BI semantic model"? Enable the setting will automatically add all tables and views in the SQL analytics endpoint to the default Power BI semantic model. If are not using the default Power BI semantic model for reporting purposes, please manually disable the “Sync the default Power BI semantic model” setting to avoid adding objects automatically.

4. If it doesn't match the above, please let me know how you added the tables.

^{Best Regards,}

^{Jarvis Tang}

^{If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.}

[Airscape]

Thank you for the response. First this is not the default semantic model. That is not used at all. I did take your advice to disable automatic adding of new tables.  I built this custom semantic model from scratch. All table were chosen from the same SQL endpoint. This has been changed many times over the past 3 months as new data has become available.  The problem now is I can't add any new tables from the same SQL endpoint it fails every time. I did clear the cache and refresh but same result.  When I tried just now I got this error:

Activity ID: d843110a-53d1-4587-aa90-424fe364c777
Request ID: c8229ede-e9af-4d03-9dc3-6b094eccfcf2
Correlation ID: b8e0b630-78d4-d0b5-fd5f-3f82a5a5ba00
Status code: 500
Time: Fri Aug 09 2024 06:54:34 GMT-0500 (Central Daylight Time)
Service version: 13.0.23878.59
Client version: 2407.5.20266-train
Cluster URI: https://wabi-us-central-a-primary-redirect.analysis.windows.net/

I have also tried to rebuild the SM from scratch I can;t do that either. It let's me add about 10-12 tables but when I try the full set of 33 tables it fails with similar errors.  

[Airscape]

This was the text in the error message:

We couldn't add or remove tables

{"error":{"code":"ExternalServiceFailed","pbi.error":{"code":"ExternalServiceFailed","parameters":{},"details":[{"code":"ModelingServiceError_Reason","detail":{"type":1,"value":"Error in ModelingEngineHost"}},{"code":"ModelingServiceError_Location","detail":{"type":1,"value":"ModelingEngineHost is failed"}},{"code":"ModelingServiceError_ExceptionType","detail":{"type":1,"value":"InvalidOperationException"}},{"code":"ModelingServiceError_Message","detail":{"type":1,"value":"There is no transaction in this session."}}]}}}

[Ankitachelani]

Hi, I am getting the same error and I have deleted all the relationships but still I can't add new tables. Infact, I tried to create a new model as well but even there I get the same error. Can Someone please help?

[SorenHou]

It did not help for me to delete the relationships. I needed to correct the column data type. I don't know if the "edit tables" run with the relationship on the last run or what happens.