20220505 Power BI Developers - Site Mgmt.; Rest APIs

Owned by Ann Crawford (Unlicensed)
Last updated: May 05, 2022
2 min read

Meeting Details

Date/Time/Location


Attendees

AttendeePresentNotes
Eric Johnstone

(tick)


Adam Sottosanti (Deactivated)

(error)


Mike Smith

(error)


Mara Morrison

(error)
Ann Crawford (Unlicensed)(tick)
Mark Norstedt(error)

Amy Pasko

(tick)
Kam Kunimoto

(error)


Kevin Wu

(error)
Michael Nesbit (Unlicensed)(tick)
Darshan Etz

(tick)


Anna Lin

(error)


Santosh Rajput

(tick)


Dawn Gregory

(tick)


Ankit Chhalotre

(tick)


Kara Nowell

(tick)


Susan Harris(tick)
Roger Chen

(tick)


Diana Antova

(error)


Tedi Tehrani(error)
Nathan Yee(error)
Katie Mankins(error)
Jessica Dewett(error)
Pam Layton(error)
Julie Inami(error)
Lisa Goto

(tick)


Alyssa Keehan (Unlicensed)(error)

Sev Palmer

(tick)
Amber Laningham

(tick)


Drew Jose(tick)
emilysanjuan@ucsb.edu(error)


Meeting Goals and Expected Preparation

Goals

  • Push the use cases and processes for Power BI
  • Solve any questions if needed.
  • Site Management - Develop comprehensive PBI report to list all items in PBI site - dataflows, datasets, reports, security and automate tasks such as refresh, deployment 

Helpful Preparation

  1. Create a github account and see if you can access https://github.com/ucsb/ucsb-powerbi
  2. Review your content in PBI usage  Usage Report 

Agenda

TimeTopicOwner
5Welcome - questionsGroup Discussion 
5

Site Management

  • inventory - use to create a pbi report of all pbi entities. This will help standardize, eliminate duplicate code and help users find what is needed
  • automate tasks such as refresh, deployment 
  • /wiki/spaces/PB/pages/17138876539


Group Discussion
10

Review/Restructure GitHub Repo

suggestions for managing code

Make sure you can access the repo - you will need a github account which takes about 5 minutes to make

https://github.com/ucsb/ucsb-powerbi


Group discussion
25

Review prototype power shell script

Site Inventory Report will be developed using the following tools:

  • Power Shell
  • Mark Norstedt has a prototype power shell script for getting all access for graddiv workspaces.  We will review and see how to make this generic for the PBI site.
  • PBI Rest APIs
  • VS Code


Mark Norstedt
5

Metrics

Gen 2 App

App Location: https://app.powerbi.com/groups/me/apps/bcaf75d2-86e0-4e5b-814f-6f5cf4ba23ac Workspace Location: https://app.powerbi.com/groups/808da81f-e4d6-4630-8bb0-417c40362382/list

Usage Report 

all

Discussion

  • Users will need access to the PBI repo.
  • The creation of the report will focus on creating the data using power shell and rest apis.  Users that are adept at visualization will craft the report from the data. 
  • Reviewed the power shell example provided by Mark Norstedt
  • Reviewed the structure in git repo https://github.com/ucsb/ucsb-powerbi. Amy Pasko and Eric Johnstone proposed the following folder structure
    • Add a folder for each of the PBI Artifacts: Data Sources, Reports, Workspaces, Data Flows, Gateways, Apps, Licenses, Groups
    • Add folder called "Code" under each Artifact
    • Add folder for a given code base as needed. e.g. PowerShell, SQL, C#, Python, Json
  • The Power shell scripts will be a combination of scripts that need admin privilege's, most likely a service account, and scripts that can be run by users on artifacts that they have access to. 
  • How to handle secrets needs to be solved.
  • We will start with a PowerShell script that generate a list of all dataflows, using PBI rest APIs.   
  • Amy Pasko it is important to comment code.
  • Eric Johnstone it is good to have samples that users can reference.
  • Eric Johnstone - there are 3 service accounts with site admin access that do not require MFA.  These can be used to execute the power shell scripts for the inventory report.

Future Discussions

Eric Johnstone can help with VS power shell environment and using commandlets and rest apis to query Power BI objects. 

 Action Items