Description
Power BI Desktop loads PBIP report artifacts only at open time. When PBIP files are modified externally (Git pulls, merge conflict resolutions, scripted refactors), those changes are not reflected in an already opened Desktop session, requiring manual close and reopen.
This limits the effectiveness of PBIP in Fabric‑first, Git‑based, collaborative development scenarios.
Why This Matters (Fabric & Git)
PBIP is foundational for Fabric CI/CD and Git integration. In real-world team workflows:
- Developers pull changes from Git while Desktop is open
- Merge resolutions and scripted updates modify PBIP files on disk
- Desktop cannot reload or apply those changes without restarting
This breaks collaborative development, slows iteration, and makes applying Git merges to active reports error‑prone.
Proposed Solution
Add an explicit “Reload from Disk” command for PBIP projects in Power BI Desktop.
- Discards in‑memory state
- Reloads PBIP artifacts from disk
- Equivalent to close & reopen, but controlled and safe
(Optional future enhancement: detect external changes and prompt the user.)
Impact
- Enables Git‑collaborative PBIP workflows
- Allows applying merges and scripted refactors without restarting Desktop
- Improves Fabric CI/CD and developer productivity
- Increases PBIP adoption for enterprise teams
on:
Add a Git-tracked “resources” folder to Lakehouses
on:
Add native Dev/Test/UAT/Prod semantic model compar...
on:
Computed Columns in Fabric Data Warehouse
LiLiu_Fabric
on:
Deployment Pipeline Run in Fabric monitor