Forum Discussion

Chiedozie's avatar
Chiedozie
New Member
2 years ago

Incomplete data in model when collaborating on project files

Power BI project files support version control with Git, which is exciting. I have noticed an inconsistent data storage in the model of the project file. The data in a model need to be refreshed each time you use git to collaborate on a project file. New data loaded into a model needs to be refreshed for each new device that uses that project file. Which shouldn't be so especially if you are working with large datasets that could take an hour to refresh.

 

Has anyone else noticed this or know a better way to preserve data stored in project files when working collaboratively using git?

2 Replies

  • Hello Chiedozie,

     

    To work collaboratively and more efficiently with Power BI and Git, maybe consider this:

     

    1. Instead of sharing the .pbix file itself, you can publish your reports to the Power BI Service, and share the report link with your team. Then, schedule refreshes or refresh datasets manually as needed.

    2. If feasible, separate the data model from the presentation layer. This means you'll have one .pbix file for the data model and another .pbix file for the report visuals. The data model file can be refreshed separately and less frequently. 

    3. There are tools and services designed to make version control easier with Power BI. One such tool is PBIXtract, which can break a .pbix file down into its constituent parts, making it more amenable to version control.

     

    Should you require my further assistance, please do not hesitate to reach out to me.

  • Thank you for you response and recommendations. The purpose of using pbip file and not pbix is that you can't work collaboratively on a pbix file. So it's already out of the question. Pbip files are made to work well with git. Differnet members in a team can make changes independently and later merged in an efficient way. Power BI project files already separates files into dataset folder and report folder. The only problem is the need to refresh the data when you load the report on a new device that doesn't already have the folder.