Power BI Versioning

[jaryszek]

Hi Guys,

i found possibility to version semantic models in power bi service:

https://learn.microsoft.com/en-us/power-bi/transform-model/service-semantic-model-version-history#op...

but what about reports versioning? 
How youare handling it within your companies?
What is a workflow?

Best,
Jacek

[Deku]

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

[jaryszek]

One more thing, 

"PBIR is still buggy for some edge cases, like losing tagging that a page is tooltips" --> what does it mean exactly? 

Opening pbix from it will be not working like it should and loose tagging?

Best,
Jacek

[Deku]

If you publish a report that has a page tooltip. The tick on the page that specifies it as a tooltip gets lost while publishing with API 

[jaryszek]

Ok so :
1. Create report in pbix file.
2. Publish using for example this kind of api?:

POST https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/imports?datasetDisplayName={datasetName}&nameConflict={Overwrite/Ignore/Abort}

[Deku · Accepted solution]

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.

[jaryszek]

You are the best mate!

Thank you very much

[jaryszek]

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

[Deku]

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

[jaryszek]

What about versioning pbix files like NAme_Version1, Name_Version2...It is making a sense? 

[jaryszek]

thank you very much