Error : InvalidRequest_DatamartNotFound

[pezakas]

Hello i am getting the following error when i am trying to refresh a direct lake semantic model in Fabric uat environment :
Data source error{"error":{"code":"DM_InvalidRequest_DatamartNotFound","pbi.error":{"code":"DM_InvalidRequest_DatamartNotFound","parameters":{"ErrorMessage":"Couldn't find generic artifact with object id: --database connection id--, with artifactType: 2000"},"details":[],"exceptionCulprit":1}}}
I also get the same error message when trying create a visualization with this semantic model data from power bi desktop.

For the record:

1. i have pushed this semantic model through a deployment pipeline from dev
2. i have set the deployment rules with dev/uat connection credentials 
3. i have checked that my semantic model is connected properly with the uat lakehouse
4. i have alternatively created another cloud connection with OAuth 2.0 authentication method instead of single sign-on but doesnt seem to change anything.

any ideas why this is happening?

[v-dineshya]

Hi @pezakas ,

Thank you for reaching out to the Microsoft Community Forum.

You are facing the "InvalidRequest_DatamartNotFound" error when refreshing a Direct Lake semantic model in the Fabric UAT environment and also when trying to create visualizations in Power BI Desktop. Please check below reasons.

1. The object ID used in the semantic model doesn’t match any valid datamart or lakehouse in the target environment.

2. The deployment pipeline didn’t correctly update the connection references during promotion from Dev to UAT.

3. The semantic model is still pointing to a Dev artifact due to incomplete rule application.

Please check below things to fix the issue.

1. Validate Object ID Mapping, Open the semantic model in Power BI Desktop. Check the data source settings and confirm that the lakehouse connection is pointing to the correct UAT object ID. If needed, rebind the model manually to the UAT lakehouse.

2. Rebuild or Rebind the Semantic Model, If the object ID mismatch persists, consider rebuilding the semantic model in UAT using the correct lakehouse reference. Use Tabular Editor or Power BI REST API to script the rebind process if manual steps are too difficult.

3. Clear Direct Lake Cache, Use a Spark notebook connected to the UAT lakehouse to run a cache-clearing command. This forces Fabric to re-read the schema and may resolve metadata issues.

4. Check for Schema Changes, check that the lakehouse schema like tables, columns, relationships in UAT matches what the semantic model expects. If schema changes occurred post-deployment, refresh the model in Power BI Desktop to re-sync metadata.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[pezakas]

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.
 

[v-dineshya]

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

[pezakas · Accepted solution]

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.

[suparnababu8]

Hi @pezakas 

The similar kind of issue reported earlier in Fabric community forum. If you haven;t visited this, kindly go thorugh this Solved: Re: Datamart was not found error between two tenan... - Microsoft Fabric Community

I would recommend you to raise a ticket with Microsoft Fabric support team. How to raise a support ticket Microsoft Fabric Support and Status | Microsoft Fabric 

Please let me know if it helps you!

Thank you!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

[pezakas]

Hello @suparnababu8 ,

Thank you for the fast response.
I visited the similar kind of issue you linked and i think they are not quite similar anyway. I believe this is a different case while the only similar is the error message.