Forum Discussion
Native Git Source Control – Report_Import_FailedToImportReport
Hi,
We have configured native Git integration with Azure DevOps and Power BI. Previously, there was a split between the Dataset and Report, with the Report .pbix live connected to the Dataset. Let’s refer to the Dataset .pbix as Sales DS and the report .pbix as Sales.
I saved both Sales DS and Sales with the new .pbip format. I then removed the Sales DS.Report folder and the Sales DS.pbip file. After that, I adjusted the definition.pbir file in Sales.Report folder to be connected to the local Sales DS.Dataset instead of the cloud connection used previously. It now looks like this:
It works as intended when I use Power BI Desktop locally with the Sales.pbip file. However, when I update the content between the Power BI workspace and the connected Git repository from Azure DevOps, I can publish the dataset, but I encounter this error for the report:
When I retry I also get this error:
It is possible to publish directly from Power BI Desktop to the Power BI workspace. However, this is not something we would like to do since we don’t want to bypass our Azure DevOps Git repository. We only want the workflow to go one way and not from Power BI services back to the Azure DevOps Git repository. Sometimes it works, sometimes it doesn't. What am I doing wrong?
Thank you for guiding us. We tried many different ways of solving this based on your recommendation, and this is the solution that worked for us: Probably not the best workaround solution, but at least it works.
1. Disconnect workspace from Git
2. Save as .PBIP and put the folders and files in a separate local folder that is not the local Git folder.
3. Publish from PBI desktop to correct workspace that we disconnected in step 1.
4. Connect workspace to Git again.
6. Sync content from PBI Services to Git.
7. We are missing the .PBIP file in our local git folder so we need to fix this.
8. To solve this we do a pull request from VS Code instead of doing a clone of repository.
9. We do a manual copy of the .PBIP file, we used in step 3, to our local Git folder.
10. We need to process the data in the local PBI model otherwise we get a conflict in PBI services.
11. Commit as usual and then we have the pbip file and everything is working as intended. We can now sync content between Git repo and PBI Services.
8 Replies
RuiRomanoMS Have you encountered this before internally?
We are working to provide more details on Git integration error messages.
Can you please retry and paste here the full error detail text?
Since you can publish, I suggest you do the following to get a clean PBIP:
- disconnect the workspace from Git
- publish from Desktop to the workspace
- connect the workspace to Azure DevOps and export
- clone the repo from ADO and confirm if you can open in Desktop and commit changes back to workspace
Thank you for guiding us. We tried many different ways of solving this based on your recommendation, and this is the solution that worked for us: Probably not the best workaround solution, but at least it works.
1. Disconnect workspace from Git
2. Save as .PBIP and put the folders and files in a separate local folder that is not the local Git folder.
3. Publish from PBI desktop to correct workspace that we disconnected in step 1.
4. Connect workspace to Git again.
6. Sync content from PBI Services to Git.
7. We are missing the .PBIP file in our local git folder so we need to fix this.
8. To solve this we do a pull request from VS Code instead of doing a clone of repository.
9. We do a manual copy of the .PBIP file, we used in step 3, to our local Git folder.
10. We need to process the data in the local PBI model otherwise we get a conflict in PBI services.
11. Commit as usual and then we have the pbip file and everything is working as intended. We can now sync content between Git repo and PBI Services.
