Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

This will be a single page to note links and discussion in the Thursday PBI developer meeting 9 am to 10 am

https://ucsb.zoom.us/j/223753798

2/15/2024

2/1/2024

Mark Norstedt will present version control on PBI. We will discuss pros and cons.

1/4/2024

Agenda

  • questions from users

    • Marsha Robertson connecting power bi to dev ops data for FMM project

    • Other questions?

  • Questions from 12/7/23

  • Source control

Source Control Process Design

Combine, pipelines and git and reduce power BI complexity.

There are two distinct processes for Power BI version control transitioning current content and continuous development.

Transitioning Current Content

Many reports and datasets in the production pipeline cannot be exported and edited in power bi desktop. Often pipelines have not been consistently used. Some data in prod not in dev. Export all reports that can be edited in the prod environment and check into the main branch.

Main devops location for all Power BI source code is https://dev.azure.com/etsesi.

  1. Remove Dev pipeline and replace all development with a user development workspace WS_Dev_<netid>. “Since a workspace can only be connected to a single branch at a time, it's recommended to treat this as a 1:1 mapping. However, to reduce the amount of workspace it entails, consider these options:

    • If a developer set up a private workspace with all required configurations, they can continue to use that workspace for any future branch they create. When a sprint is over, your changes are merged and you're starting a fresh new task, just switch the connection to a new branch on the same workspace. You can also do this if you suddenly need to fix a bug in the middle of a sprint. Think of it as a working directory on the web.

    • Developers using a client tool (such as VS Code, Power BI Desktop, or others), don’t necessarily need a workspace. They can create branches and commit changes to that branch locally, push those to the remote repo and create a pull request to the main branch, all without a workspace. A workspace is needed only as a testing environment to check that everything works in a real-life scenario. It's up to you to decide when that should happen. “ (microsoft best practices for life cycle management)

12/7/2023

Agenda

  • questions from users

    • How to view the notes/history of deployments added/done via a Deployment Pipeline?

    • Review source code control workflow for .rdl files and classic PBI report files

10/26/2023

Agenda

10/12/2023

Agenda

Notes

The reports must be saved as a PBIP file (PBI project). This feature is in preview and must be enabled on your power bi desktop. Go to Files> Options and Settings > Options > preview features > check box power BI Project(.pbib) save option.

References

Git and power bi - Power BI Desktop projects (PBIP) - Power BI | Microsoft Learn

download tabular editor https://www.sqlbi.com/tools/tabular-editor/

pbi git video https://youtu.be/OdkS7DF7ElY

workspace settings for git https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=commit-to-git

  • No labels