Forum Discussion
Resolver IPower BI GIT everything is suddenly uncommitted
Microsoft product team confirmed, that unfortunately, we do not have a choice. The only way to move on is to accept the changes and commit them: a) all Workspaces one by one into Git, or b) from the March 2024 PBI Desktop -> Git -> Workspaces, as I mentioned above.
The fastest way is option (a), but If your Git branch connected to the workspaces (e.g. main branch) doesn't allow direct commits (only Pull Requests) then you'll have to disable the commit policy, commit all from workspaces, enable the commit policy back and then resolve all conflicts that the developers will have.
Advocate IIHi all, we have the same issue. It is caused by March 2024 Power BI update:
https://powerbi.microsoft.com/en-us/blog/power-bi-march-2024-feature-summary/#post-26258
wiSama is right, I compared the updated files in Power BI service with Git repo, and it seems that Power BI service has changed all files in all workspaces connected to Git automatically by removing files item.metadata.json and item.config.json and adding new .platform file.
Depending on your branching strategy there are some options:
1. Commit all changes from workspaces into Git, but it might create conflicts which you will need to resolve manually.
2. Undo all changes in the workspace, open all reports in March version of PBI Desktop, commit changes and sync Git into all workspaces. This is something similar to what Anonymous suggested, but without disconnecting from Git.
We have dozens of workspaces and hundreds of datasets and reports. I raised MS support ticket to find the best way of how to resolve this.
Resolver IWill be really helpful if you can post Microsoft response 🙂
- alexgor87
Microsoft product team confirmed, that unfortunately, we do not have a choice. The only way to move on is to accept the changes and commit them: a) all Workspaces one by one into Git, or b) from the March 2024 PBI Desktop -> Git -> Workspaces, as I mentioned above.
The fastest way is option (a), but If your Git branch connected to the workspaces (e.g. main branch) doesn't allow direct commits (only Pull Requests) then you'll have to disable the commit policy, commit all from workspaces, enable the commit policy back and then resolve all conflicts that the developers will have.