Forum Discussion
Power BI Versioning
- 1 year ago
Create in pbix
Save as pbip
Commit and stage changes to git
Push to remote repo
Deploy with git integration connected to workspace, or with fabric APIs
Details on processes and options here
https://learn.microsoft.com/en-us/power-bi/developer/projects/
If you want to work with bpix files you would best off using SharePoint as saving files on top of other provides a list of versions.
Pbip format and git, to keep track of history. Deploy via fabric APIs, git integration or manually with desktop.
In public preview so would be careful. TMDL is fine and stable, PBIR is still buggy for some edge cases, like losing tagging that a page is tooltips. If you don't use pbir you can go back from pbip to pbix
Thnak you very much.
What about doing descriptions and enumarating version in Power Bi ? pbix with specific version is published and git description with version also (or git tag)?
Best,
Jacek
- Deku1 year agoSuper User
You can keep a changelog.md in the repo or just rely on commit messages. Also can a have a parameter in model with version number, which you increment.l with version bumps. Would use tag to take specific commits that represent a version bump