Dataset Workload failed to import the dataset
Power BIIn general form, with the parts that change in brackets:
Workload Error Code Dataset_Import_FailedToImportDataset Workload Error Message Dataset Workload failed to import the dataset with dataset id [id]
Fabric Git integration could not import a semantic model from the repository into the workspace. The message names no file and no cause. In both threads quoted here, the fault was in the service.
- Usually
- A DAX calculated table, which a Microsoft employee called a bugA source renamed in Power Query
- Fix
- Publish the report and semantic model to the workspace by hand, then sync back to Git and choose Keep Incoming Changes, as one poster did.
Check your project opens the Report Doctor with this message filled in. The text travels in the URL fragment, which browsers never send to a server.
How the message appears
Copied exactly from each source. A name in square brackets replaced one from someone else's project.
Workload Error Code Dataset_Import_FailedToImportDataset Workload Error Message Dataset Workload failed to import the dataset with dataset id [dataset id]
What causes it
A DAX calculated table, which a Microsoft employee called a bug
In one thread a user found the import failed for a model with a DAX calculated table. Their workaround was to replace that table with one imported from Excel. A Microsoft employee replied that it is a bug they would fix.
Source: Source Control - Dataset Workload failed to import the dataset with dataset id[1].
The Report Doctor can't detect this, because it was a bug in the Fabric service, not a fault in the files.A source renamed in Power Query
In another thread it started after the schema and view name of a source were changed in Power Query. The poster published the report and model by hand, then synced back to Git with Keep Incoming Changes. The answer marked as the solution says the product team fixed it.
Source: GIT - Dataset Workload failed to import the dataset with dataset id[2].
The Report Doctor can't detect this, because the failure was in the Fabric service, which the product team fixed, not in the files.
The fix
Publish the report and semantic model to the workspace by hand, then sync back to Git and choose Keep Incoming Changes, as one poster did. If the model has a DAX calculated table, one user got past it by importing that table instead.
In tables/Dates.tmdl:
partition Dates = calculated
mode: import
source = CALENDARAUTO()7 lines change.
partition Dates = m
mode: import
source =
let
Source = Excel.Workbook(Web.Contents("https://[tenant].sharepoint.com/[site]/Dates.xlsx"), null, true),
Dates = Source{[Item = "Dates", Kind = "Table"]}[Data]
in
DatesIn one thread the import failed on a model with a calculated table, and replacing it with an imported table got past it. A Microsoft employee called the failure a bug.
The Power BI Report Doctor cannot find this. In both cases the fault was in the Fabric service, not in the files.
For the other messages a project can stop on, listed by the file that causes each, see Power BI Desktop can't open a PBIP.
Worth knowing
- This message comes from Fabric Git integration, when it imports a semantic model from the repository.
Sources
- [1]Microsoft forum: Source Control - Dataset Workload failed to import the dataset with dataset id. The original post (2023-09-13), a user's reply about a DAX calculated table, and a Microsoft employee's reply that it is a bug. Read 2026-11-08.
- [2]Microsoft forum: GIT - Dataset Workload failed to import the dataset with dataset id. The original post (2024-05-22) and Community Support's reply marked as the solution. Read 2026-11-08.
Did this page help?
Your answer helps us know what to improve and what you find useful.