Not able to create relationships or create measures in SQL endpoint

[aasmuau]

When I try to create relationships in the model view or create measures in my SQL endpoint in my lakehouse, I get the following error:

[charrington]

Hi
just to mention I got the same issue yesterday when trying to create relationships. For some table I was able to create them, but some not, without logical reason. Even thought I checked the cardinality (1 to many etc) and make sure the relation is making sense.

This was the error, similar to the one mentionned in this post:
Underlying Error: {"code":"ExternalServiceFailed","pbi.error":{"code":"ExternalServiceFailed","parameters":{},"details":[{"code":"ModelingServiceError_Reason","detail":{"type":1,"value":"An internal error occurred."}},{"code":"ModelingServiceError_Location","detail":{"type":1,"value":"Datamart Workload"}},{"code":"ModelingServiceError_ExceptionType","detail":{"type":1,"value":"DatamartServerException"}},{"code":"ModelingServiceError_Message","detail":{"type":1,"value":"An internal error occurred."}},{"code":"ModelingServiceError_ExceptionErrorCode","detail":{"type":1,"value":"InternalError"}}]}}
Activity ID: 1ba1da9d-3aa8-40ae-b24b-f579c3b5ed53
Correlation ID: 813b1fe1-fb66-160e-8ca5-7ec4dfbfd1a2
Request ID: 7d40b46d-4845-bc0f-c487-6557b3e09bdc
Status code: 500
Time: Thu Nov 02 2023 14:53:08 GMT-0400 (Eastern Daylight Time)
Service version: 13.0.21891.85
Client version: 2310.4.16370-train
Cluster URI: https://wabi-south-central-us-redirect.analysis.windows.net/

A few hours later I came back and tried the same exact thing, and it worked!!

This is really weird and looks more like a bug to me.

Also @v-nikhilan-msft I don't understand your long response about upgrading SQL, the version compatibility, etc. don't you know that this SQL engine is completely generated by Microsoft Fabric, and we don't have any control over it? I feel you are missing the context here. The Fabric SaaS is intented to provide infra/software completely running on the cloud, so why are you discussing like if we can act on this?

Also it's not because you cannot reproduc the issue that it doesn't happen on our side.

My problem was solved by itself, but this feels a little unstable for now.

Thanks

[v-nikhilan-msft]

Hi @charrington ,
Apologies for the issue you have been facing.

Thanks for providing the information regarding the error. I have reached to the internal team for looking into this. I will keep you posted regarding the updates.
Fabric is still under preview, and we are working hard to address any issues that are discovered. We appreciate your patience and understanding as we continue to improve Fabric.

I appreciate your feedback and I will use it to improve my responses in the future.

[charrington]

Thanks for the reply. Sorry I was maybe a little rude...we all understand that Fabric is in preview and things are not 100% reliable. But that's why I think the community feedback is important. I just wanted to restate some facts and orient you guys in the right direction.

Have a good day

[v-nikhilan-msft]

Hi @charrington ,

No worries at all, I appreciate your feedback. It's important to me that I am able to provide accurate and helpful information, even if it is about a product that is still under development.

I agree that the community feedback is very important. It helps me to learn about the issues that people are facing and to improve my responses. I also appreciate your help in orienting me in the right direction.

I hope that I can continue to provide you with helpful information and support in the future. Have a good day as well!

[v-nikhilan-msft]

Hi @aasmuau ,
Thanks for using Fabric Community.
Apologies for the issue you have been facing. I tried to create a new relationship between two tables in my Lakehouse. There was no such error. I have attached the screenshots for your reference.

The error message you are getting indicates that the modeling service is unable to save your changes to the server because it references an object or property that is not available in the current edition of the server or the compatibility level of the database. This can happen for a few reasons:

• The server is running an older version of SQL Server than the client you are using to create the relationships or measures.
• The compatibility level of the database is lower than the version of SQL Server that the server is running.
• The object or property that you are referencing has been deprecated in the current version of SQL Server.

To fix this error, you need to identify the cause of the problem and take the appropriate action.

If the server is running an older version of SQL Server than the client, you need to upgrade the server to a newer version.

If the compatibility level of the database is lower than the version of SQL Server that the server is running, you need to upgrade the compatibility level of the database. To do this, you can use SQL Server Management Studio (SSMS).

Hence try creating the relationship between the tables after following the above steps.
If the issue still exists, this might require a deeper investigation from our engineering team about your workspace and the logic behind it to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team :

https://support.fabric.microsoft.com/support

After raising the ticket please share the details here as it would help us to track for more information.
Thank you.

Hope this helps. Please let us know if you have any further queries.

[v-nikhilan-msft]

Hi @aasmuau ,
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Please let us know if you have any further queries.

[v-nikhilan-msft]

Hi @aasmuau ,
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Please let us know if you have any further queries.