Forum Discussion
Dataset_Import_FailedToImportDataset
I just talked to Microsoft support and they helped me work through this issue. Here's what I had to do.
1. In PBI Service, from the workspace where Dataset_Import_FailedToImportDataset occurred, create a new branch as decribed in this article.
2. Open the affected report(s) in PBI Desktop and publish to the service
3. In the PBI workspace, validate the the conflict has been resolved and commit the changes to the branch created in step 1.
4. Merge the branch back into the source
5. Swap the workspace back to the source branch
I'm experiencing similar behavior. I have a development branch where I made a few changes using version 2.128.952.0 (24.04). If I try to sync my workspace with that branch, any files updated using that version show a conflict and I get the error:
Workload Error Code Dataset_Import_FailedToImportDataset
Workload Error Message Dataset Workload failed to import the dataset with dataset id <id>
If I switch the workspace branch back to main, where the files were updated with version 2.127.1327.0 (24.03), all of the datasets / reports synchronize as expected.
I just talked to Microsoft support and they helped me work through this issue. Here's what I had to do.
1. In PBI Service, from the workspace where Dataset_Import_FailedToImportDataset occurred, create a new branch as decribed in this article.
2. Open the affected report(s) in PBI Desktop and publish to the service
3. In the PBI workspace, validate the the conflict has been resolved and commit the changes to the branch created in step 1.
4. Merge the branch back into the source
5. Swap the workspace back to the source branch
Hi steveplatz2 ,
I had the same issue as mentioned above, but what I tried to do, was simply just publish the report manually to the workspace and sync back into Git, resolving the Git conflict with Keep Incoming Changes.
But, do you know, if Microsoft is working on this issue, because the mentioned steps is just a workaround.Barre I don't know if this is an issue that Microsoft is working to correct or not. No indication was given on my call.
