Power BI Git Integration

[Rosy081]

I need to know why is the download report disabled for reports that we undo after deletion from staging environments while using azure devops based Git Integration. If this is the case then it would be useless to use azure devops based git integration for version control that after revert we cannot download the reports. Can someone give me more information on this topic. Is it so necessary that we use VScode or pbip project to push to Git rather than pushing the reports from power bi service to azure devops based.

If possible kindly share the documentations to the limitations as well. I only use git integration for report versions and not for complete project development hence all my reports are pushed to main branch just for historization of report. 

Suggest me best practices or best way to use it or best way to have a history of reports that can be downloaded in case of accidental deletion

[v-tsaipranay]

Hi @Rosy081 ,

Thank you for reaching out to the Microsoft Fabric Community. 

Also, thank you @pborah  for your valuable inputs. His response is correct and aligns with Microsoft’s best practices. Using the .pbip format is recommended because it removes underlying data, reducing file size and improving security  especially for large reports, as supported in Power BI Projects documentation. Organizing your DevOps repo by workspace folders is also a smart approach to keep things clean, especially in larger environments. However, while .pbip helps with version control, it won’t fix the issue of reports becoming non-downloadable after an undo. This happens due to how report states are managed. To prevent data loss, we recommend keeping periodic backups using .pbit templates or saving occasional .pbix copies. Combining .pbip, a structured repo, and regular backups ensures better version control and recovery.

I hope my suggestions give you good idea, if you need any further assistance, feel free to reach out.

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

Thank you. 

[v-tsaipranay]

Hi @Rosy081 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-tsaipranay]

Hi @Rosy081 ,

I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.

If my response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.

Thankyou.

[v-tsaipranay]

Hi @Rosy081 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[pborah · Accepted solution]

@Rosy081 we also use devops based git intregration. While I have not rolled back to a previous version for any of my reports yet, I will recommend the pbip format for pushing to devops because it strips out the underlying data which is good both security wise as well as file size. We have reports where the pbix file can be as large as 500-600 megs. We were using git repos even before git integration became available or pbip came along. We simply saved our reports as templates and pushed to repo back then.

The other thing I will recommend is organizing your devops repo by folders for each of your workspaces in service. But I guess that depends on how big your organization and powerbi tenant is. We have hundreds of reports across 30+ workspaces (60+ if you count both test and prod) so we cannot afford to have the clutter in our repo.