Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
We now constantly update the data model to tailor for business requirement changes. However, a release of model to PBI leads to new dashboard development. Developers implement new dashboard changes.
New releases of data models affect the development work already done. Developers have to incoorporate their previous changes to the released new models. This creates more work and inconsistencies and testings.
Are there better ways to handle these constantly released data models ?
Thanks,
Timmy
Hi @timleung,
My only suggestion could be that trying creating new models instead of updating the existing model if possible, and just create some new reports/dashboards, and last pin them together in a single dashboard on Power BI service. Or I don't think there is a way to update the data model without affecting the reports/dashboards which are already created.
Regards
Thanks v-ljerr-msft !
Is there any intermediate backup file that can be used to store all new reports/dashboards ? Then, after model updates, the backup file can be implemented on the top of new changes.
Or, is there other best practices to constantly promote model changes ?
Thanks,
Timmy
So we have to record all new reports/dashboards. This may prompt to inconsistency should this be done not carefully. Is there any pbi system files that can be used to save changes ? Is there new features from MS PBI to handle changes in the middle of development cycles ?
Really appreciate your replies !
Timmy
User | Count |
---|---|
15 | |
2 | |
1 | |
1 | |
1 |
User | Count |
---|---|
16 | |
11 | |
5 | |
4 | |
3 |