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

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?

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.