Source control - Dataset Workload failed to import the dataset. Cannot resolve all the paths.

[notsobad__]

Hello, we are using Source Control Synced with Azure Devops in our Workspaces.
We have the  it divided to 3 branches dev/test/prod for each of 3 types of workspaces also dev/test/prod.

The workflow is simply, we deliver new features in DEV, then we do PR with those changes into Test and then finally to prod.

We've got few problem when trying to update changes from git especially after pushing into test. On DEV everything works, but after pushing that code into Test and trying to get those changes in source control we have error as follows

Workload Error Code Workload_FailedToParseFile

Workload Error Message Dataset Workload failed to import the dataset with dataset id 8c5463b1-b3c0-49d8-8b2f-b321e5c6ec3d. Cannot resolve all the paths while de-serializing Database. Resolution Errors: Property ToColumn of object "relationship <oii>7031c9e3-392e-8b1a-2adf-a7ae521f6cdc</oii>" refers to an object which cannot be found

This semantic model is connected to another semantic model. And the changes included some columns hiding.

The only way to fix it for now is to disconnect the workspace, delete old report and sync it once again.. however I don't want to do it so often, because it should work out of the box. I dont have time to first remove the content from published app, do changes, delete report, disconnect, connect,sync, do the app once again.

[collinq · Accepted solution]

Hi @notsobad__ ,

This error message often happens when you have a semantic model that references another semantic model.  OR, perhaps a column or table used in the relationships of queries/tables has been hidden or deleted.  OR, you don't have the right permissions set up between workspaces if this report/semantic model is using a semantic model in another workspace.  Do any of these apply?

[v-echaithra]

Hi @notsobad__ ,

I hope the information is helpful. May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-echaithra]

Hi @notsobad__ ,

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Best Regards,
Chaithra E.

[v-echaithra]

Hi @notsobad__ ,

I hope the information provided is helpful. I wanted to check whether you were able to resolve the issue with the provided solutions. Please let us know if you need any further assistance.

Thank you.

[v-echaithra · Accepted solution]

Hi @notsobad__ ,

The error you're facing typically happens when your dataset references another semantic model (like a data source or model from another workspace), and that reference is not correctly configured or is broken, the import fails.
So ensure that any semantic models your dataset relies on are correctly synced and accessible from the Test environment. Check if the referenced models exist and are up-to-date.

See if you have any Hidden or Deleted Columns/Tables. If a column or table used in relationships or queries has been hidden or deleted in DEV but not properly updated in Test, this could cause a deserialization error. Check if any columns or tables have been hidden, renamed, or deleted in DEV that might affect relationships. Ensure these changes are properly reflected in the Test environment.
If your report/semantic model uses a semantic model from another workspace, there could be permission issues preventing access to the necessary resources.Double-check the permissions between workspaces to ensure that the Test workspace has the correct access to any external models or datasets it relies on.

1st Check: Ensure that all referenced semantic models, columns, and tables exist and are correctly configured in the Test workspace.

2nd Check: Verify that permissions are set correctly between workspaces, especially if external models are involved.

3rd Check: Review any recent changes in DEV (e.g., hidden/removed columns or models) and make sure those are reflected in the Test workspace.

[collinq · Accepted solution]

Hi @notsobad__ ,

This error message often happens when you have a semantic model that references another semantic model.  OR, perhaps a column or table used in the relationships of queries/tables has been hidden or deleted.  OR, you don't have the right permissions set up between workspaces if this report/semantic model is using a semantic model in another workspace.  Do any of these apply?