Forum Discussion
Error : InvalidRequest_DatamartNotFound
- 1 year ago
Yes i confirm that the mistake was that the semantic model on UAT was connected to the Lakehouse id instead of the sql analytics endpoint. Once i changed the id in the deployment pipeline and the connection everything was aligned.
Thank you.
Hello v-dineshya ,
I appreciate your fast response.
While viewing the lineage on both workspaces , i found out that my semantic model on dev is connected directly to the SQL analytics endpoint and then the SQL analytics endpoint is directly connected to the Lakehouse. While in uat, i see that the semantic model is directly connected to the Lakehouse.
So:
DEV = Lakehouse->SQL analytics endpoint->Semantic model
UAT = Lakehouse->Semantic model
Then i checked again the data source creds and i confirmed the above by checking the urls from both Lakehouse and SQL analytics endpoint.
I will try to create a new cloud connection this time using the SQL analytics endpoint id instead of the Lakehouse one in order to directly connect the semantic model with the SQL analytics endpoint and i will let you know.
Hi pezakas ,
Thank you for your response. As you mentioned in your previous response, You are trying to create a new cloud connection using SQL analytics endpoint id to directly connect to semantic model. Once you have done with connection, Please do let us know. Please provide ETA for your response. It will help us to follow-up.
Regards,
Dinesh
- pezakas1 year agoHelper I
Yes i confirm that the mistake was that the semantic model on UAT was connected to the Lakehouse id instead of the sql analytics endpoint. Once i changed the id in the deployment pipeline and the connection everything was aligned.
Thank you.