Failed to export item - The following item failed to export to Git

[JakeJess]

Hi,

We have configured native Git integration with Azure DevOps and Power BI. 

We are getting a error message when updating Power BI Service from our ADO Repos. This only happens the first time we publish from our repository to Power BI Service. The error pops up and disappears without having to fix anything.

The error:

 

The error message pops up when the update from Git goes through but as soon as you press the close button the report and dataset syncs up and the error is gone. This also makes it hard to solve the problem as the error "fixes" itself. The error only appears in Power BI Service, we don't get any issues when pushing from our local repository to ADO Repos or when merging to the main branch.  We are trying to understand why this error pops up. 

Has anyone else seen this problem?

[v-yajiewan-msft]

Hi @JakeJess, 

For similar issues, we recommend you try the following workaround steps to see if they solve your issue:

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.

 

Solved: Re: Native Git Source Control – Report_Import_Fail... - Microsoft Fabric Community

Best regards,

Joyce

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[JakeJess]

Hi, 

This would work, the only problem with that solution is that we don't want to disconnect/connect our workspace everytime we publish a new report as we are more than one developer in the team. The problem here is we get a error that "fixes" itself and we don't understand why. We can't solve the problem as it disappears right after we are finished syncing the workspace. 

@RuiRomanoMS Have you encountered this problem before?

[RuiRomanoMS]

Looks like a bug. Can you tell me more about the report you are trying to sync? Can you repro this with any report? Can you share a repro report with me?

[JakeJess]

We are using a design template, this might be the reason why. The error does not occur when publishing a report that has a live connection to an already published dataset, or when starting up a blank report and loading data without the template. Could it be the deisgn template that we use that are the root of the problem, and if so how can we solve this?

This is the full error message that we get:

With the template I have tried both importing it with the .pbit file and also having the design template as a .pbix file and the saving it in the local repository as .pbip as we can't have it as .pbip from the start because the reportid in the .pbip needs to be unique. 

[RuiRomanoMS]

WHat do you mean by "design template"? Can you provide some repro steps or files?

[JakeJess]

Well as we are a development team that is growing we want to make sure that we all follow the same standards. So the design template contains preset visuals that we fill out with the data for that specific report (with some room for changes). We have also built up a structure for the semantic model. This is to make sure that the semantic models follow the same standard for self service reports and if another developer has to take over the work from someone else. The design template is our template for best practices to ensure that we deliver a great end result.

Steps:

1. Open up design template .pbix
2. Import tables 
3. Work on project
4. Save to local repository as .pbip
5. Create a new branch for your progress in VSCode
6. Commit and push to ADO Repository
7. Create Pull request
8. Merge into main 
9. Sync in Power BI Service. (This is where we get the error)