Forum Discussion
Development team working in same dashboard at the same time
Hi Amy, thanks for your response.
I know this is hard to diggest but actually I'm not looking for help with a particular development on Power BI but help on how to define best practices (and maybe use other tools) for having a large development team working in same file at the same time.
So, generally speaking I want to pass from Overall Profit v1
Having three different developers working in parallel in the same file.
Let's review the progress on dashboard over time:
2019-09-18: We have our Overall Profit v1 and our developers create their own copies Overall Profit v1_1, Overall Profit v1_2 and Overall v1_3 (we said that tasks complexity is 3-2-1 from easier to harder to implement).
2019-09-19: Developer for task 3. finishes his work on it so now Overall v1_3 can be deployed and let's stop here for a moment.
At this point Overall Profit v1_1 and Overall Profit v1_2 are work in progress versions and they don't have changes made in Overall v1_3 and since the changes include bookmarks is not only a matter of copy-paste objects from one dashboard to other.
So we have a decision to make:
Either Other developers should replicate Overall v1_3 changes in their own copies (this can lead to errors)
or they know that Overall v1_3 is already done and as soon as they finish their changes (2. is more likely to be done soon than 3.). If their changes are way too big (we put 30 bookmarks creation in 2. and radical data model, measures and visualizations changes in 3. for making them big changes) developers must almost redo their work at some point in time (the more time passes between developers ending their tasks, the more complicated merging changes it gets).
2019-09-23: Developer of task 2. finishes his work. On 2019-09-19 we decided to redo the advances that he had at the moment, so his version has all changes so far.
2019-10-10: Developer of task 1. finishes her work (it took her so long because changes were big ones and were impacting several visualizations and tables). Now she's facing a challenge: how should she proceed applying changes?
Should she redo all of her work in latest version (containing changes from 3. and 2.) or should her take her copy and try to merge others work on it, the later with high probability of adding errors to final dashboard since she doesn't know for sure what changes have been done to dashboard.
So questions are:
- How to merge from this point?
- Can we use a different technique than the one used by this development team?
- Can we benefit somehow by using source control like GIT or because .pbix is binary file and we have no other exporting option for dashboard, we're out of luck?
I hope is clearer now with dashboards versions.
I'm wondering if you ever figured something out from this. I lead a team of 5 bi engineers and the best thing we can come up with is one person working on one report at a time (if you can only imagine managing the product having everyone working on different things...)