Forum Discussion
Native Git Source Control – Report_Import_FailedToImportReport
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.
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.Thanks for sharing.
I wonder why you need to create the PBIP file? Not sure if you knew, but the PBIP file is optional and you can always open in desktop by opening the \Report\definition.pbir.
https://learn.microsoft.com/en-gb/power-bi/developer/projects/projects-overview#open-a-power-bi-projectThe main reason is that we only want to develop locally and sync it one way from Power BI Desktop through Git repo and then from Git repo to Power BI Services. The most important aspect for us is that we can track changes made either in the model or in the report.