Power BI Pipelines have been very helpful in CI/CD process between dev/test/prod workspaces - WHEN artifacts are created in Power BI Desktop and published to the service.
Now, we are hoping to move more towards in-service development and cut out the Power BI Desktop. However, the deployment piplinee does not detect/recognize changes to a reported that are done in the service. For example, a business edits a report in the production workspace - adding a new page and chart visual. The pipleine does not recognize that edit, so it can easily be overwritten by a future update from the dev/test workspace.
Reasons for adopting in-service development:
- Microsoft continues to improve the in-service development capabilities. Recent releases allow createion and editing of semantic models and reports in the service.
- Some artifacts can only be created in service, such as dataflows. Org apps is another artifact type that may qualify.
- We want to expand Power BI adoption outside of IT department into the hands of business users. Our goal for IT to create robust semantic model and then for business users to create their own reports using the avilable in service tools. For business users, creating a report or chnaging an existing report in service may be the easiest, least technical way.
lbendlin
on:
Fabric Copy Activity Upsert Needs Native Audit Col...
on:
Power BI Subscriptions enhancements sorely needed
on:
Ragged Hierarchy Display options in Matrix Visual
miguel
on:
Personalized Source List in Get Data