Introduction



The Power of SharePointSummary: This paper explores how to build out a basic project-management app based on SharePoint lists and three key technologies that integrate with SharePoint Online: PowerApps, Microsoft Flow, and Power BI. These three technologies are all part of the Microsoft business platform, which makes it easy to measure your business, act on the results, and automate your workflows.Writer: Michael BlythePublished: March 10, 2017Applies to: SharePoint Online, PowerApps, Microsoft Flow, Power BIThis document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious.? No real association or connection is intended or should be inferred.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. ? 2017 Microsoft. All rights reserved.Contents TOC \o "1-3" \h \z \u Introduction PAGEREF _Toc477171062 \h 5Business scenario PAGEREF _Toc477171063 \h 6Getting started quickly PAGEREF _Toc477171064 \h 6Prerequisites PAGEREF _Toc477171065 \h 6Task 1: Set up SharePoint lists PAGEREF _Toc477171066 \h 7Step 1: Understand the lists PAGEREF _Toc477171067 \h 7Step 2: Create and review the lists PAGEREF _Toc477171068 \h 8Step 3: Update connections to samples - optional PAGEREF _Toc477171069 \h 11Task 2: Create an app for project requests PAGEREF _Toc477171070 \h 15Step 1: Generate an app from a SharePoint list PAGEREF _Toc477171071 \h 15Step 2: Review the app in PowerApps Studio PAGEREF _Toc477171072 \h 15Step 3: Customize the app’s browse screen PAGEREF _Toc477171073 \h 16Step 4: Customize the app’s details screen and edit screen PAGEREF _Toc477171074 \h 18Step 5: Run the app from the list PAGEREF _Toc477171075 \h 20Formula deep-dive (1) - optional PAGEREF _Toc477171076 \h 21Task 3: Create a flow to manage project approval PAGEREF _Toc477171077 \h 23Step 1: Configure the flow template PAGEREF _Toc477171078 \h 23Step 2: Create actions for Approve = YES PAGEREF _Toc477171079 \h 26Step 3: Create actions for Approve = NO PAGEREF _Toc477171080 \h 31Step 4: Run the approval flow PAGEREF _Toc477171081 \h 37Task 4: Create a project management app PAGEREF _Toc477171082 \h 39Quick review of PowerApps Studio PAGEREF _Toc477171083 \h 39Step 1: Create screens PAGEREF _Toc477171084 \h 40Step 2: Connect to a SharePoint list PAGEREF _Toc477171085 \h 42Step 3: Build the SelectTask screen PAGEREF _Toc477171086 \h 43Step 4: Build the AssignManager screen PAGEREF _Toc477171087 \h 46Step 5: Build the ViewProjects screen PAGEREF _Toc477171088 \h 51Step 6: Build the UpdateDetails screen PAGEREF _Toc477171089 \h 55Step 7: Run the app PAGEREF _Toc477171090 \h 59Formula deep-dive (2) - optional PAGEREF _Toc477171091 \h 63Task 5: Create a Power BI report PAGEREF _Toc477171092 \h 64Quick review of Power BI Desktop PAGEREF _Toc477171093 \h 64Step 1: Get data into Power BI Desktop PAGEREF _Toc477171094 \h 67Step 2: Improve the data model PAGEREF _Toc477171095 \h 73Step 3: Create report visualizations PAGEREF _Toc477171096 \h 80Task 6: Publish the Power BI report and create a dashboard PAGEREF _Toc477171097 \h 92Task 7: Set up data alerts PAGEREF _Toc477171098 \h 99Task 8: Embed a Power BI report in SharePoint PAGEREF _Toc477171099 \h 103Summary PAGEREF _Toc477171100 \h 108Step 1: Add a project to the Project Requests list PAGEREF _Toc477171101 \h 108Step 2: Approve the project PAGEREF _Toc477171102 \h 109Step 3: Assign a manager to the project PAGEREF _Toc477171103 \h 111Step 4: Add time estimates for the project PAGEREF _Toc477171104 \h 113Step 5: Review report data for existing projects PAGEREF _Toc477171105 \h 115Step 6: Respond to pending project delays PAGEREF _Toc477171106 \h 118IntroductionDo you have SharePoint Online and want to better automate and streamline your business processes? Have you heard of PowerApps, Microsoft Flow, or Power BI, but you’re not sure how to use them with SharePoint Online? You’ve come to the right place! This paper explores how to build out a basic project-management app based on SharePoint lists and three key technologies that integrate with SharePoint Online: PowerApps, Microsoft Flow, and Power BI. These three technologies are all part of the Microsoft business platform, which makes it easy to measure your business, act on the results, and automate your workflows. When you’re done with this paper, you will have a cool scenario like the following:Business scenarioIn this paper, the company Contoso has a SharePoint Online site where they manage the lifecycle of projects, from request, to approval, to development to final review. A project requestor, such as a department head, requests an IT project by adding an item to a SharePoint list. A project approver, such as an IT manager, reviews the project, and then approves it or rejects. If approved, the project is assigned to a project manager, and additional detail is added to a second list through the same app. A business analyst reviews current and completed projects using a Power BI report embedded in SharePoint. ?Microsoft Flow is used to send approval email and respond to Power BI alerts.Getting started quicklyThe scenario we present in this paper is simple compared to a full-blown project management and analysis app, but it still takes some time to complete all the tasks. If you just want a quick introduction to using PowerApps, Microsoft Flow, and Power BI with SharePoint, check out the following articles:PowerApps: Generate an app from within SharePoint using PowerApps and Generate an app to manage data in a SharePoint listMicrosoft Flow: Wait for approval in Microsoft FlowPower BI: Embed with report web part in SharePoint OnlineWhen you’re done, we hope you’ll be back to check out this full scenario. Even within the scenario, you can focus on the tasks that interest you, and complete the tasks as you have time. After you set up SharePoint lists in task 1, you can work through tasks 2-5 in any order; then tasks 6-8 are sequential. Lastly, we have included two finished apps and a Power BI Desktop report as part of the download package for this scenario. You can look at these and learn by example even if you don’t go through all the steps in each task.PrerequisitesTo complete the scenario, you need the following subscriptions and desktop tools.Subscription or toolLinkOffice 365 Business Premium subscriptionTrial subscriptionPowerApps subscriptionTrial subscription (click Sign up free)PowerApps Studio for WindowsFree download (use PowerApps Studio for web if not on Windows)Microsoft Flow subscriptionTrial subscription (click Sign up free)Power BI Pro subscriptionTrial subscription (click Sign up)Power BI DesktopFree download (click Download)Ideally, you have basic familiarity with each technology, but you can still complete the scenario if you’re new to some of these technologies. Use the following content to get up to speed:Get started with SharePointPowerApps Guided LearningFlow Guided LearningPower BI Guided LearningTask 1: Set up SharePoint listsSharePoint has a ton of features for sharing and collaboration, but we will focus on one feature for this scenario: SharePoint lists. A list is just a collection of data that you can share with team members and other site users. We’ll review the lists, then you can create them in your own SharePoint Online site.Step 1: Understand the listsThe first list is Project Requests, where a project requestor adds a request. The project approver then reviews the request and approves or rejects it.List ColumnData TypeNotesTitleSingle line of textDefault column, used for project nameDescriptionSingle line of textProjectType Single line of textValues: new hardware, upgraded hardware, new software, upgraded softwareRequestDateDateRequestorSingle line of textEstimatedDaysNumberEnables comparison of requestor estimate to project manager estimate to actualApprovedSingle line of textValues: pending, yes, noNote: We also use the ID column, which is generated by SharePoint and hidden by default. We use basic data types for simplicity, but a real app might use more complex types, like Person or Group for the Requestor column. For information on data types supported by PowerApps, see Known issues.The second list is Project Details, which tracks details for all approved projects, like which project manager is assigned.List ColumnData TypeNotesTitleSingle line of textDefault column, used for project nameRequestIDNumberMatches the value in the Project Requests list ID columnApprovedDateDateStatusSingle line of textValues: not started, in progress, completedProjectedStartDateDateWhen the project manager estimates that the project will startProjectedEndDateDateWhen the project manager estimates that the project will endProjectedDaysNumberWorking days; would typically be calculated, but isn’t in this scenarioActualDaysNumberFor completed projectsPMAssignedSingle line of textProject managerStep 2: Create and review the listsTo continue with the scenario, you need to create the two SharePoint lists and populate them with sample data. We’ll show you how to do this by creating the list and pasting sample data into it. Note: use Internet Explorer for this step. In Internet Explorer, in your SharePoint site, click or tap New, then List.Enter the name “Project Requests”, then click or tap Create.The Project Requests list is created, with the default Title field.Add columns to the list:Click or tap , then Single line of text.Enter the name “Description”, then click or tap Create.Repeat steps a. and b. for the other columns in the list:Single line of text > “ProjectType”Date > “RequestDate”Single line of text > “Requestor”Number > “EstimatedDays”Single line of text > “Approved”Copy data into the list:Click or tap Quick edit.Select the cells in the grid.Open the project-requests.xlsx workbook and select all the data (not the headings).Copy the data and paste it into the grid in SharePoint, then click or tap Done.Repeat the list creation and copy process for the “Project Details” list, using the project-details.xlsx workbook. Refer to the table above for the column names and data types.Step 3: Update connections to samples - optionalAs noted earlier, we included two sample apps and a report in the download package. You can complete this scenario without using these samples, but if you want to use the samples, you need to update the connections to the SharePoint lists. You update them so that they use your lists as a data source, rather than ours.Update connections for the sample apps:Open project-management-app.msapp in PowerApps Studio for Windows.Click or tap Allow, so that PowerApps to use SharePoint.On the ribbon, on the Content tab, click or tap Data sources.In the right pane, click or tap the ellipsis (. . .) next to Project Details, then click or tap Remove.In the right pane, click or tap Add Data Source.Click or tap New connection. Click or tap SharePoint, then Connect.Enter the URL for the SharePoint Online site that contains the lists you created, then click or tap Go.Select the Project Details list, then click or tap Connect.The Data sources tab in the right pane now shows the connection that you created.In the right pane, click or tap the ellipsis (. . .) next to Project Details, then click or tap Refresh.Click in the upper right corner to run the app, and make sure the connections work properly.Repeat the steps in this section for project-requests-app.msapp, using the Project Requests list.Update connections for the sample reportOpen project-analysis.pbix in Power BI Desktop.On the ribbon, on the Home tab, click or tap Edit queries, then Data source settings.Click or tap Change Source.Enter the URL for your SharePoint Online site, then click or tap OK.Power BI Desktop displays a banner under the ribbon, so you can apply changes and bring in data from the new source. Click or tap Apply Changes.Sign in with an organizational account (the account you use to access SharePoint Online), then click or tap Connect.Task 2: Create an app for project requestsNow that the SharePoint lists are in place, we can build and customize our first app. PowerApps is integrated with SharePoint, so it’s easy to generate a basic three screen app directly from a list. This app allows you to view summary and detailed information for each list item, update existing list items, and create new list items. If you create an app directly from a list, the app appears as a view for that list. You can then run that app in a browser, as well as on a mobile phone.Tip: The download package for this scenario includes a finished version of this app: project-requests-app.msapp.Step 1: Generate an app from a SharePoint listIn the Project Requests list you created, click or tap PowerApps, then Create an app.Give the app a name, like “Project Requests app”, then click or tap Create. When the app is ready, it opens in PowerApps Studio for web.Step 2: Review the app in PowerApps StudioIn PowerApps Studio, click or tap each screen in the left navigation bar to review that screen in the middle pane. There are three screens:The browse screen, where you browse, sort, and filter the data pulled in from the list. The details screen, where you view more detail about an item, and edit or delete the item.The edit/create screen, where you edit an existing item or create a new one.Step 3: Customize the app’s browse screenClick or tap the browse screen. This screen has a layout that contains a gallery to show list items, as well as other controls, like a search bar and sort button.Select the BrowseGallery1 gallery by clicking or tapping any record except the first one.In the right pane, update the fields to match the following list:RequestDateDescriptionTitleRequestorWith BrowseGallery1 still selected, select the Items property.Change the formula to SortByColumns(Filter('Project Requests', StartsWith(Title, TextSearchBox1.Text)), "Title", If(SortDescending1, Descending, Ascending)). This allows you to sort and search by the Title field, instead of the default that PowerApps picked. See Formula deep-dive (1) for more information.Click or tap File, then Save. Click or tap to go back to the app.Step 4: Customize the app’s details screen and edit screenClick or tap the details screen. This screen has a different layout that contains a display form to show the details for an item selected in the gallery. It has controls to edit and delete items, and to go back to the browse screen.Select the DetailForm1 display form.In the right pane, drag the Title field to the top.Click or tap the edit screen.This screen contains an edit form to edit the selected item, or create a new one (if you come here directly from the browse screen). It has controls to save or discard changes.Select the EditForm1 edit form.As above, drag the Title field to the top.Step 5: Run the app from the listIn the Project Requests list, click or tap All Items, then Project Requests app.Click Open, which opens the app in a new browser tab.In the app, click or tap for the first item in the browse gallery.Click or tap to edit the item.Update the Description field – change the last word from “group” to “team,” then click or tap .Close the browser tab.Go back to the Project Requests list, click or tap Project Requests app, then All Items.Verify the change you made from the app.This is a pretty simple app, and we only made a few basic customizations, but you can see it’s possible to quickly build something interesting. We’re going to move on to the next task, but look around the app a little more if want, and see how the controls and formulas work together to drive app behavior.Formula deep-dive (1) - optionalThis section is optional, but it will help you understand more about how formulas work. In step 3 of this task, we modified the formula for the Items property of BrowseGallery1. Specifically, we changed the sort and search to use the Title field, instead of the field that PowerApps picked. Here’s the modified formula:SortByColumns ( Filter ( 'Project Requests', StartsWith ( Title, TextSearchBox1.Text ) ), "Title", If ( SortDescending1, Descending, Ascending ) )But what does this formula do? It determines the source of data that appears in the gallery, filters the data based on any text entered in the search box, and sorts the results based on the sort button in the app. The formula uses functions to do its work; each highlighted part below is a function: SortByColumns ( Filter ( 'Project Requests', StartsWith ( Title, TextSearchBox1.Text ) ), "Title", If ( SortDescending1, Descending, Ascending ) )Functions take parameters (i.e. input), perform an operation (like filtering), and return a value (i.e. output):The SortByColumns function sorts a table based on one or more columns.The Filter function finds the records in a table that satisfy a formula that you specify.The StartsWith function tests whether one text string begins with another.The If function returns one value if a condition is true, and returns another value if the same condition is false.When you put the functions together in the formula, here’s what happens:If you enter text in the search box, the StartsWith function compares that text to the start of each string in the Title column of the list.StartsWith ( Title, TextSearchBox1.Text )For example, if you enter “de” in the search box, you see four results, including items that start with “Desktop” and “Device.” You won’t see all the “Mobile devices” items because those don’t start with “de.” The Filter function returns rows from the Project Requests table. If there is no text in the search box to compare, Filter returns all rows. Filter ( 'Project Requests', StartsWith ( Title, TextSearchBox1.Text )The If function looks at whether the variable SortDescending1 is set to true or false (the sort button in the app sets it). The function then returns a value of Descending or Ascending.If ( SortDescending1, Descending, Ascending )Now the SortByColumns function can sort the gallery. In this case, it sorts based on the Title field, but this can be a different field than the one you search on.If you stuck with us up to this point, we hope you have a better sense of how this formula works, and how you can combine functions and other elements to drive the behavior your apps require. For more information, see Formula reference for PowerApps.Task 3: Create a flow to manage project approvalIn this task we’ll create a flow that drives the process of approving projects. Flow is integrated with SharePoint, so it’s easy to create a flow directly from a list. The flow we’ll create is triggered when an item is added to the Project Requests list. The flow sends an email to the project approver, who approves or rejects the request directly in email. The flow then sends an approval or rejection email to the project requestor and updates our SharePoint lists appropriately.Step 1: Configure the flow templateIn the Project Requests list, click or tap Flow, then Create a flow.In the right pane, click or tap Send approval email when a new item is added.If you’re not already signed in, sign into SharePoint and Outlook, then click or tap Continue.You now see the template for this flow, ready for you to complete. The boxes in the flow represent steps. They take input from previous steps, as well as input that you provide. Each step can then provide output to subsequent steps. For example, the Send approval email step gets list information from the previous step, uses the email address you provide, and outputs an approve or reject value to the next step.Enter a valid email address in the To box. The address should resolve to a name in your tenant, as shown in the following image.The next box in the flow responds to the project approver’s email and routes the flow to one of two branches: IF YES or IF NO.Step 2: Create actions for Approve = YESIn the IF YES branch, click or tap the Send email box.By default, an email is sent to the person who created the list item, with the subject line and message body that you see. You can update these if you like.Click or tap Add an Action.Under Choose an action, search for “SharePoint”, then click or tap SharePoint – Update item.Enter the SharePoint site URL and list name.Select the ID box, then click or tap ID in the dynamic content dialog box. Dynamic content is available throughout the flow, based on previous steps. In this case, the SharePoint list information is available, and we can use it in the actions that we create.Select the Title box, search for “Title” in the dynamic content dialog box, then click or tap Title.In the Approved box, enter “Yes”. This part of the flow should now look like the following image.Click or tap Add an Action again. This time we’ll add an item to the Project Details list for the project that was approved.Under Choose an action, search for “SharePoint”, then select SharePoint – Create item.Enter the SharePoint site URL and list name.Select the Title box, search for “Title” in the dynamic content dialog box, then click or tap Title.Select the RequestId box, then click or tap ID in the dynamic content dialog box. In the PMAssigned box, enter “Unassigned”. This part of the flow should now look like the following image.Step 3: Create actions for Approve = NOBy default, there are no actions at all for this branch. We will create an email to send to the project requestor, and update the Project Requests list. We won’t add an item to the Project Details list because the project isn’t moving forward.In the IF NO branch, click or tap Add an Action.Under Choose an action, search for “Outlook”, then select Office 365 Outlook – Send an email.In the To box, add Created By Email from the dynamic content dialog box.In the Subject and Body boxes, add Title from the dynamic content dialog box.Add to the subject and body of the email, as in the following image.Now we’ll update the Project Requests list. Click or tap Add an Action.Under Choose an action, search for “SharePoint”, then select SharePoint – Update item.Enter the SharePoint site URL and list name.Select the ID box, then click or tap ID in the dynamic content dialog box. Select the Title box, search for “Title” in the dynamic content dialog box, then click or tap Title.In the Approved box, enter “No”. This part of the flow should now look like the following image.At the top right of the screen, click or tap Create flow, then Done.The flow is now complete, and it should look like the following image if you collapse the boxes.Step 4: Run the approval flowIn the Project Requests list, click Quick Edit and add an item like the following:Title = “New monitor for Megan”Approved = “Pending”Description = “Megan needs a 24” monitor”EstimatedDays = “1”ProjectType = “New hardware”RequestDate = “02/03/2017”Requestor = “Megan Bowen”Click Done at the top of the page when you’re finished.Check the inbox of the approver’s email account. You should have an email like the following.Note that the email is sent to the approver, Allan DeYoung. It is sent from Megan Bowen, because she set up the flow.After you click Approve or Reject, the flow runs another process, and you get feedback like the following directly in the email.The flow sends an email to Megan with Allan’s response, as in the following image. This email also comes from Megan because she owns the flow.Task 4: Create a project management app In this task, we’ll build an app from scratch. This app allows a user to assign a manager to projects and to update project details. You will see some of the same controls and formulas you saw in the first app, but you will build more of the app yourself this time. The process is more complex, but you’ll learn more, so we think it’s a fair trade-off.Tip: The download package for this scenario includes a finished version of this app: project-details-app.msapp.Quick review of PowerApps StudioYou used PowerApps Studio for web in the last task, but we want to make sure you understand all the parts before we move on. You can continue to work in PowerApps Studio for web, but we recommend using PowerApps Studio for Windows, mostly because you can undo changes if you make a mistake (which is not possible in the web version at the time of this writing.)PowerApps Studio has three panes and a ribbon that make app creation feel like building a slide deck in PowerPoint:Left navigation bar, which shows thumbnails of all the screens in your appMiddle pane, which contains the app screen you are working onRight-hand pane, where you set options like layout and data sourcesProperty drop-down list, where you select the properties that formulas apply toFormula bar, where you add formulas (like in Excel) that define app behaviorRibbon, where you add controls and customize design elementsStep 1: Create screensWith that review out of the way, let’s start building an app. In this step, we’ll create four blank screens for the app. We’ll build these screens out in later steps.ScreenPurposeSelectTaskOpening screen; navigate to other screensAssignManagerAssign a manager to an approved projectViewProjectsView a list of projects, with summary informationUpdateDetailsView and update the details for a projectIn PowerApps Studio for Windows, click or tap New, then under Blank app, click or tap Phone Layout.Save the app to the cloud:Click or tap File, which opens to an App settings tab. Enter the name “Project Management app”.Click or tap Save as, verify that app will save to the cloud, then click Save in the lower right corner. Click or tap to go back to the app.On the Home tab, click or tap Screen1, then rename the screen to SelectTask.Create and rename additional screens:On the Home tab, click or tap New screen, then rename that screen to AssignManager.Repeat the previous step for the other screens: ViewProjects and UpdateDetails.The app should now look like the following image.Step 2: Connect to a SharePoint listIn this step, we’ll connect to the Product Details SharePoint list. We only use one list in this app, but you could easily connect to both if you want to extend the app. In the left navigation bar, click or tap the SelectTask screen.In the middle pane, click or tap connect to data.In the right pane, click or tap New connection.Click or tap SharePoint, then Connect.Enter a SharePoint URL, then click or tap Go.Select the Project Details list, then click or tap Connect.The Data sources tab in the right pane now shows the connection that you have created. Step 3: Build the SelectTask screenIn this step, we’ll provide a way to navigate to the other screens in the app—working with some of the controls, formulas, and formatting options that PowerApps provides. In the left navigation bar, click or tap the SelectTask screen.On the Home tab, click or tap Layout, then select the layout at top left.In the middle pane, select the default [Title], then in the formula bar, update the Text property to “Contoso Project Management”. Insert introductory text:On the Insert tab, click or tap Text box, then drag the text box down below the top banner.In the formula bar, set the following properties for the text box:Color property = DarkGraySize property = 18Text property = “Click or tap a task to continue...”Add two navigation buttons:On the Insert tab, click or tap Button, then drag the button below the text box.In the formula bar, set the following properties for the button:OnSelect property = Navigate(AssignManager, Fade). When you run the app and click this button, you navigate to the second screen in the app, with a fade transition between the screens. Text property = “Assign Manager”Resize the button to accommodate the text.Copy the button and paste it below the first one, so you can create a second button with some different properties.Set the following properties for the second button:OnSelect property = Navigate(ViewProjects, Fade).Text property = “Update Details”Run the app. The app doesn’t do a lot yet, but you can run it if you like:Click or tap the SelectTask screen (the app always starts from the selected screen).Click or tap in the upper right corner to run the app.Click or tap one of the buttons to navigate to another screen.Click or tap in the upper right corner to close the app.Save the app.Step 4: Build the AssignManager screen In this step, we’ll add a gallery to display all projects that have been approved but don’t yet have a manager. We’ll add other controls, so you can assign a manager. Note: We’ll build a page later in the app that allows you to edit all fields for a project (including the manager field), but we thought it would be cool to show you how to build a screen like this one as well.In the left navigation bar, click or tap the AssignManager screen.Update the screen layout like you did for the SelectTask screen:Change the layout style to include a blue bar at the top.Change [Title] to Assign Manager.Add a text box with the following properties:Color property = DarkGraySize property = 18Text property = “Select a project, then assign a manager”Add a back arrow to return to the SelectTask screen:Click or tap the blue bar at the top of the screen.On the Insert tab, click or tap Icons, then click or tap Left.Move the arrow to the left side of the blue bar, and set the following properties:Color property = WhiteHeight property = 40OnSelect property = Navigate(SelectTask, Fade)Width property = 40Add and modify a gallery:On the Insert tab, click or tap Gallery, then Text gallery – Vertical.The gallery is inserted with default text.Set the following properties for the gallery:BorderThickness property = 1BorderStyle property = DottedItems property = Filter('Project Details', PMAssigned="Unassigned"). Only projects with no manager assigned are included in the gallery.In the right pane, update the fields to match the following list:ApprovedDateTitleStatusSelect the title in the first gallery item, and set the following properties:Size property = 16. FontWeight property = BoldResize text boxes in the gallery as appropriate. The screen should now look like the following image.Change the color of an item if it’s selected:Select the gallery, then set the TemplateFill property to If (ThisItem.IsSelected=true, Orange, White).Select an item in the gallery. The screen should now look like the following image.Add a text box, text input, and OK button to submit manager assignments:Click or tap outside the gallery you’ve been working on.On the Insert tab, click or tap Text box. Drag the button below the gallery, to the left. Set the following properties for the text box:Size property = 20Text property = “Manager:”On the Insert tab, click or tap Text, then Text input. Drag the text input below the gallery, in the center. Set the following properties for the drop down:Height property = 60Size property = 20Width property = 250 On the Insert tab, click or tap Button. Drag the button below the gallery, to the right. Set the following properties for the button:Height property = 60OnSelect property = Patch('Project Details', LookUp('Project Details', ID = Gallery1.Selected.ID), {PMAssigned: TextInput2.Text}). For more information, see Formula deep-dive (2).This formula updates the Project Details list, setting a value for the PMAssigned field.Size property = 20Text property = “OK”Width property = 80 The completed screen should now look like the following image.Step 5: Build the ViewProjects screenIn this step, we’ll add a gallery to the ViewProjects screen, like the gallery in the first app that we generated. This gallery provides a lot of functionality with minimal effort. The gallery displays items from the Project Details list. You select an item on this screen, then you edit the details on the UpdateDetails screen.In the left navigation bar, click or tap the ViewProjects screen.On the Home tab, click or tap Layouts, then select the layout you see in the following image.PowerApps builds a complete screen, and inserts a gallery with default text.In the blue bar at the top of the app, click or tap [Title]. In the formula bar, set the Text property to “View Projects”.Select the refresh button , and set its OnSelect property to Refresh('Project Details').Select the new item button , and set its OnSelect property to NewForm(Form2); Navigate(UpdateDetails, ScreenTransition.None). Add a back arrow to return to the SelectTask screen:Click or tap the blue bar at the top of the screen.On the Insert tab, click or tap Icons, then click or tap Left.Move the arrow to the left of the refresh button in the blue bar, and set the following properties:Color property = WhiteHeight property = 40OnSelect property = Navigate(SelectTask, Fade)Width property = 40Change the data source for the BrowseGallery2 gallery:Select the BrowseGallery2 gallerySet the Items property of the gallery to SortByColumns(Filter('Project Details', StartsWith(Title, TextSearchBox1.Text)), "Title", If(SortDescending1, Descending, Ascending)).This sets the data source of the gallery to the Project Details list, and uses the Title field for search and sort.Select the in the first gallery item, and set the OnSelect property to Navigate(UpdateDetails, None). In the right pane, update the fields to match the following list:StatusTitlePMAssignedThe completed screen should now look like the following image.Step 6: Build the UpdateDetails screenIn this step, we’ll add an edit form and related controls to the UpdateDetails screen. On this screen, you edit details for a project that you selected on the View Projects screen.In the left navigation bar, click or tap the UpdateDetails screen.Update the screen layout like you did for the AssignManager screen:Change the layout style to include a blue bar at the top.Change [Title] to Update Details.Add an edit form to the screen:On the Insert tab, click or tap Forms, then Edit.Drag the form below the blue bar, then drag the bottom handle so the form covers the rest of the screen.Set the following properties for the form:DataSource property = 'Project Details'Item property = BrowseGallery2.SelectedWith the form still selected, in the right pane click or tap the eye icon for each field in the following order:TitlePMAssignedStatusProjectedStartDateProjectedEndDateProjectedDaysActualDaysAdd controls to submit and reset the form:Click or tap the blue bar at the top of the screen.On the Insert tab, click or tap Icons, then click or tap Check.Move the check mark to the right of the blue bar, and set the following properties:Color property = WhiteHeight property = 40OnSelect property = Submit(Form2). Because we’re using the edit form control, we can use Submit() and other simple functions, instead of using Patch() like we did earlier.Width property = 40On the Insert tab, click or tap Icons, then click or tap Cancel.Move the cancel icon to the left of the blue bar, and set the following properties:Color property = WhiteHeight property = 40OnSelect property = ResetForm(Form2); Back(). This resets the form to its original values, and navigates back to the ViewProjects screen.Width property = 40The completed screen should now look like the following image (if the fields are blank, make sure you select an item on the View Projects screen).Step 7: Run the appNow that the app is complete, let’s run it to see how it works. We’ll add a link on the SharePoint site to the app. You will be able to run the app in the browser, but you might need to share the app for other people to run it. For more information, see Share your apps. First, we’ll assume the role of the project approver—we’ll look for any projects that don’t have a manager assigned, and assign a manager to one of the projects. Then we’ll assume the role of the project manager, and add some information about a project that is assigned to us. Add a link to the app:In the Office 365 app launcher, click or tap PowerApps.In PowerApps, click or tap Project Management app.Copy the address (URL) for the app in the browser.In SharePoint, click or tap EDIT LINKS.Click or tap (+) link.Enter “Project Management app”, and paste in the address for the app.Click or tap OK, then Save.Assign a manager to a project:First, let’s look at the Project Details list in SharePoint. Two projects have a value of Unassigned in the PMAssigned column. We will see these in the app.Click or tap the link that you created to the app.On the first screen, click or tap Assign Manager.On the Assign Manager screen, you see the two unassigned projects from the list. Select the New BI software project.In the Manager text box, enter “Joni Sherman”, then click OK.The change is applied to the list, and the gallery refreshes so only the remaining unassigned project is displayed.Go back to the SharePoint list. You’ll see that the project entry is now updated with the project manager name. Update details for the project:Click or tap to go back to the first screen, then click or tap Update Details.On the View Projects screen, enter “New” in the search box.Click for the New BI software item.On the Update Details screen, set the following values:The Status field = “Not started”The ProjectedStartDate field = “3/6/2017” The ProjectedEndDate field = “3/24/2017”The ProjectedDays field = “15” Click or tap to apply the change to the SharePoint list.Close the app, and go back to the list. You see that the project entry is now updated with the date and day changes. Formula deep-dive (2) - optionalThis is the second optional section on PowerApps formulas. In the first deep-dive, we looked at one of the formulas that PowerApps generates for the browse gallery in a three-screen app. In this deep-dive, we’ll look at a formula that we use for the AssignManager screen of our second app. Here’s the formula:Patch ( 'Project Details', LookUp ( 'Project Details', ID = Gallery1.Selected.ID ), {PMAssigned: TextInput2.Text} )What does this formula do? When you select an item in the gallery and click the OK button, the formula updates the Project Details list, setting the PMAssigned column to the value that you specify in the text box. The formula uses functions to do its work; each highlighted part below is a function: Patch ( 'Project Details', LookUp ( 'Project Details', ID = Gallery1.Selected.ID ), {PMAssigned: TextInput2.Text} )The Patch function modifies one or more records of a data source.The LookUp function finds the first record in a table that satisfies a formula.When you put the functions together in the formula, here’s what happens:When you click the OK button, the Patch function is called to update the Project Details list.Within the Patch function, the LookUp function identifies which row of the Project Details list to update. It does this by comparing the ID of the selected gallery item to the ID in the list. For example, an ID of 12 means that the entry for New BI software should be updated.Now that the Patch function has the right ID, it updates the PMAssigned field to the value in TextInput2.Text.Task 5: Create a Power BI reportIn this task, we’ll create a Power BI report based on the two SharePoint lists. We’ll bring the list data into Power BI Desktop and clean it up a little, do some basic data modeling, and create a set of visuals that tell us something about the data.Tip: The download package for this scenario includes a finished version of this report: project-analysis.pbix.Quick review of Power BI DesktopBefore we dive into report creation, let’s review Power BI Desktop. This is a powerful tool, with a lot of features, so we will focus on an overview of the areas that you will use in this task. There are three main work areas or views in Power BI Desktop:?Report view, Data view, and Relationships view. Power BI Desktop also includes Query Editor, which opens in a separate window.The following screen shows the three view icons along the left of Power BI Desktop: Report, Data, and Relationships, from top to bottom. The yellow bar along the left indicates the current view; in this case, Report view is displayed. Change views by selecting any of those three icons.The Report view has five main areas:The ribbon, which displays common tasks associated with reports and visualizations.The Report view, or canvas, where visualizations are created and arranged.The Pages tab area along the bottom, which lets you select or add a report page.The Visualizations pane, where you change visualizations, customize colors or axes, apply filters, drag fields, and more.The Fields pane, where query elements and filters can be dragged onto the Report view, or dragged to the Filters area of the Visualizations pane.The Data view has three main areas:The ribbon, which has the Modeling tab selected below. On this tab, you create calculated tables and columns, and make other changes to the data model.The center pane, which shows data for the selected table.The Fields pane, where you control how fields are displayed in your reports.We don’t use the Relationships view in this task, but you can check it out later after we bring the list data into Power BI Desktop.In Query Editor, you build queries and transform data, then load that refined data model into Power BI Desktop. Query Editor has four main areas:The ribbon, which has many options for shaping and transforming the data that you bring in.The left pane, where queries are listed and available for selection, viewing, and shaping.The center pane, where data from the selected query is displayed and available for shaping.The Query Settings window, which lists the query’s properties and data transform steps that have been applied. Step 1: Get data into Power BI DesktopIn this step, we’ll first connect to the two lists. Then we’ll clean up the data by removing columns we don’t need for our data analysis. We’ll also change the data types on some of the remaining columns so that calculations work properly. For more information on getting and cleaning data in Power BI Desktop, see the Getting Data section in our Guided Learning course.Connect to SharePoint lists:In Power BI Desktop, on the Home tab, click or tap Get Data, then More…In the Get Data dialog box, click or tap SharePoint Online List, then Connect.Enter the URL for your SharePoint site, then click or tap OK.If you get the following dialog box, make sure you’re signed in with the right credentials, then click or tap Connect.Select Project Details and Project Requests, then click or tap Edit.The lists are now displayed as tables in Query Editor.Remove unnecessary columns from the Project Details table:In the left navigation pane, click or tap Project Details.In the middle pane, select the FileSystemObjectType column, then click or tap Remove Columns.Remove the two columns after the Id column: ServerRedirectedEmbedURL and ContentTypeId. Tip: use the Shift key to select both columns, then click or tap Remove Columns.Remove all columns to the right of the PMAssigned column (a total of 22 columns). The table should match the following image:Remove unnecessary columns from the Project Requests table:Repeat the process you went through for Project Details, and remove all columns to the right of the Approved column (a total of 22 columns). The table should match the following image:Change the data type on Project Details columns:Select the ProjectedDays column, click or tap Data Type: Any, then Whole Number. Repeat the previous step for the ActualDays column.Select the ApprovedDate column, click or tap Data Type: Any, then Date.Repeat the previous step for the ProjectedStartDate and ProjectedEndDate columns.Change the data type on Project Requests columns:Select the EstimatedDays column, click or tap Data Type: Any, then Whole Number.Select the RequestDate column, click or tap Data Type: Any, then Date.On the Home tab, click Close and Apply to close Query Editor and go back to the main Power BI Desktop window.Click or tap File, then Save, and save with the name project-analysis.pbix.Step 2: Improve the data modelNow that we have the data from our SharePoint lists pulled into Power BI Desktop, we’ll move on to data modeling. Data modeling can be a time-consuming process, but we’ll briefly show you some interesting things you can do to get more out of the list data in Power BI Desktop:Change how the two tables are related to each otherAdd a date table so we can make calculations based on weekdaysAdd calculated columns to calculate timespans between project milestonesAdd measures to calculate variance in projected versus actual days for a projectAfter these steps are complete, we can build visualizations that take advantage of the improvements to our model. For more information on modeling data in Power BI Desktop, see the Modeling section in our Guided Learning course.Change table relationships:When Power BI Desktop brought the lists in, it created a relationship between them based on the Id column in both tables. The relationship should actually be between the Id column in the Project Requests table, and the RequestId column in the Project Details table. Let’s fix that:Click or tap the Data view icon.On the Modeling tab, click or tap Manage Relationships. We’ll stay on this tab in the Data view for all the data modeling steps.Make sure the existing relationship is selected, click or tap Delete, then Delete again to confirm.Click New to create a different relationship.In the Create Relationship dialog box:For the first table, select Project Requests, and the Id column.For the second table, select Project Details, and the RequestId column.The screen should look like the following image. When you’re ready, click or tap OK.Add a date table to make date-based calculations easier:Click or tap New Table.Enter this formula into the formula bar: Dates = CALENDARAUTO().This formula creates a table called Dates with a single date column. The table covers all dates from your other tables and updates automatically if additional dates are added (i.e. if data is refreshed). This formula and the other ones in this section use Data Analysis Expressions (DAX), a formula language for Power BI and other technologies. For more information, see DAX basics in Power BI Desktop.Press enter to create the Dates table.Add a calculated column to the Dates table:While still on the date table, click or tap New Column.Enter this formula into the formula bar: IsWeekDay = SWITCH(WEEKDAY(Dates[Date]), 1,0,7,0,1). This formula determines whether a date in the Date column is a weekday. If the date is a weekday, the IsWeekDay column gets a value of 1; otherwise it gets a value of 0.Press enter to add the IsWeekDay column to the Dates table.Add a calculated column to the Project Details table:In the right pane, click or tap the Project Details table, then New Column.Enter this formula into the formula bar: ApprovedStartDiff = CALCULATE(SUM(Dates[IsWeekday]), DATESBETWEEN(Dates[Date], 'Project Details'[ApprovedDate], 'Project Details'[ProjectedStartDate] ) )This formula calculates the difference in days between when a project was approved and when it is projected to start. It uses the IsWeekday column from the Dates table, so it counts only weekdays.Press enter to add the ApprovedStartDiff column to the Project Details table.Add a calculated column to the Project Requests table:In the right pane, click or tap the Project Requests table, then New Column.Enter this formula into the formula bar: RequestDateAge = CALCULATE(SUM(Dates[IsWeekday]), DATESBETWEEN(Dates[Date], 'Project Requests'[RequestDate], NOW() ) )This formula calculates the difference in days between when a project was requested and today’s date (NOW()). Again, the formula counts only weekdays. This column is used to look for the project that has been pending the longest.Press enter to add the RequestDateAge column to the Project Requests table.Add a measure to the Project Details tableIn the right pane, click or tap the Project Details table, then New Measure.Enter this formula into the formula bar: VarProjectedActual = DIVIDE( SUM('Project Details'[ActualDays]) - SUM('Project Details'[ProjectedDays]), SUM('Project Details'[ProjectedDays]) )This formula calculates the variance between actual and projected days for a project. We add this as a measure, rather than a calculated column, so it returns the correct results regardless of how the data is filtered or aggregated in a report.Press enter to add the VarProjectedActual measure to the Project Details table.Add a measure to the Project Requests table:In the right pane, click or tap the Project Requests table, then New Measure.Enter this formula into the formula bar: MaxDaysPending = MAXX( FILTER('Project Requests', 'Project Requests'[Approved]="Pending"), 'Project Requests'[RequestDateAge] )This formula finds the project that has been pending the longest, based on the calculated column we defined earlier.Press enter to add the MaxDaysPending measure to the Project Requests table.Step 3: Create report visualizationsNow we’re at the step that many people think of when they think of data analysis: creating visualizations so we can find patterns in our data. In this step, we’ll create four visualizations:A column chart that shows projected days versus actual days on projectsA column chart that shows the variance for each projectA card that shows the project that has been pending the longestA table that shows the time between project approval and projected start dateAfter we’ve created these report visualizations in Power BI Desktop, we’ll publish the data and reports to the Power BI service, so we can create and share dashboards. For more information on creating reports in Power BI Desktop, see the Visualizations section in our Guided Learning course.Create a bar chart to show projected versus actual:Click or tap the Report view icon. We’ll stay in this view for the rest of our time in Power BI Desktop.In the Visualizations pane on the right, click or tap Clustered column chart.Drag PMAssigned and Title from Project Details in the Fields pane to Axis in the Visualizations pane.Drag ActualDays and ProjectedDays from Project Details in the Fields pane to Values in the Visualizations pane.The visualization should now look like the following image.Drag Status from Project Details in the Fields pane to the Filters area of the Visualizations pane, then check the Completed check box.The chart is now filtered to show only completed projects, which makes sense because we are comparing projected days to actual days.Click the arrows in the upper left corner of the chart to move up and down the hierarchy of project managers and projects. In the following image, you see what the drill down into projects looks like.Create a bar chart to show variance from projected:Click or tap on the canvas outside the visualization you just created.In the Visualizations pane on the right, click or tap Clustered column chart.Drag PMAssigned and Title from Project Details in the Fields pane to Axis in the Visualizations pane.Drag VarProjectedActual from Project Details in the Fields pane to Values in the Visualizations pane.Drag Status from Project Details in the Fields pane to the Filters area of the Visualizations pane, then check the Completed check box.The visualization should now look like the following image.You can see from this chart how much more variability there is for projects that were run by Irvin Sayers versus Joni Sherman. Drill in to see the variability by project, and whether the days projected was more or less than the actual days. Before we create more visualizations, move and resize the ones you already created, so they fit side-by-side.Create a card that shows the longest pending project:Click or tap on the canvas outside the visualization you just created.In the Visualizations pane on the right, click or tap Card.Drag MaxDaysPending from Project Requests in the Fields pane to Fields in the Visualizations pane.Click or tap Format (paint roller), then set Border to On.Set Title to On, then add the title “Max days pending approval”.The visualization should now look like the following image. After we publish this report, we’ll use this tile to trigger an alert if the maximum value for a pending project reaches a certain threshold.Create a table that shows the time between project approval and projected start date:Click or tap on the canvas outside the visualization you just created.In the Visualizations pane on the right, click or tap Table.Drag PMAssigned, Title, and ApprovedStartDiff from Project Details in the Fields pane to Values in the Visualizations pane.Drag ProjectedStartDate from Project Details in the Fields pane to the Filters area of the Visualizations pane, then select all dates except for (Blank).Drag the columns of the table so you can see all the data. The visualization should now look like the following image.Click or tap the down arrow for ApprovedStartDiff, then click or tap Average, so we can see the average duration between project approval and projected start date.Click or tap the down arrow for ApprovedStartDiff again, then click or tap Conditional formatting.Use the default settings and click OK. The visualization should now look like the following image.As you can see, projects that Irvin Sayers runs tend to start a lot later after approval. There could be factors other than the assigned manager, but this would be worth looking into.That brings us to the end of the report section, and you should now have a complete report based on data imported from SharePoint and cleaned up and modeled in Power BI Desktop. If everything went according to plan, your report should look like the following image.You are now ready to publish this report to the Power BI service. Task 6: Publish the Power BI report and create a dashboardIn this task, we’ll publish our data set and report to the Power BI service; then we’ll create a dashboard based on the report. In many cases a report has a large number of visualizations and only a subset are used in a dashboard. In our case, we’ll add all four visualizations to the dashboard.Publish the data set and report:In Power BI Desktop, on the Home tab, click or tap Publish.If you’re not already signed in to the Power BI service, enter an account, then click or tap Sign in.Enter a password, then click or tap Sign in.Choose a destination for the report, then click or tap Select. We recommend publishing to a group workspace to simplify access to the report in SharePoint. In this case, we are publishing to the Project Management group workspace. For more information, see Creating groups in Power BI.After publishing completes, click or tap Open 'project-analysis.pbx’ in Power BI.The Power BI service loads the report in a browser. Click or tap the menu at the top left (a) to see the left navigation pane.You can see that when we published, Power BI Desktop uploaded a data set (d) and a report (c). You create dashboards in the service, not Power BI Desktop, and this workspace doesn’t have any dashboards yet (b). We’ll create one next. Note: Power BI has a new navigation experience coming out, and it could be enabled in your site. If the left navigation pane looks different from the above image, see The new Power BI navigation experience for more information. Configure credentials for refresh:In the service, click or tap in the top right corner, then click or tap Settings.Click or tap Datasets, then project-analysis.Expand Data source credentials, then click or tap Edit credentials.Select OAuth2 for Authentication method, then click or tap Sign in.Select or sign in to an account that has permissions for the SharePoint lists.When the process completes, you’ll get the following message in the service.Create a dashboard:In the service, click or tap the chart on the upper left, then click or tap .Enter a name for the dashboard you want to pin to, then click or tap Pin.Click or tap the chart on the upper left, then click or tap .Select the existing dashboard, then click or tap Pin.Repeat the pinning process for the other two visuals.In the left navigation pane, click or tap the dashboard name.Review the dashboard. If you click on a tile, you will go back to the report.That wraps up most of the work in Power BI. If that was your first experience creating reports and dashboards, congratulations! If you’re already a pro, we hope you could move through it quickly. Now we will add alerting to make sure we know if the dashboard needs our attention. Task 7: Set up data alertsIn this task we’ll add an alert in Power BI to let us know if pending projects are taking too long to approve, and a flow that responds when that alert occurs. For more information on alerts, see Data alerts in Power BI service.Create an alert:In the Power BI service, open the dashboard you created in the last task.On the card with the single number, click or tap the ellipsis (. . .).Click or tap .In the right pane, click or tap Add alert rule.Look at the options that are available for alerts, such as how frequently an alert should run. Enter a value of 25 for Threshold, then click or tap Save and close.The alert won’t fire right now even though 56 is above the threshold of 25. It will fire when data is updated, which we’ll see when we run through the scenario end-to-end.When the alerts fires, Power BI sends email to the creator of the alert, and we’ll see how to send additional mail using Flow, in the next step.Create a flow that responds to the alert:Sign into flow., click or tap Services, then Power BI.Click or tap Send an e-mail to any audience when a Power BI data alert is triggered.Click or tap Use this template.If you’re not already signed in, sign into Outlook and Power BI, then click or tap Continue.In the Alert Id drop-down list, select Alert for Max days pending approval.In the To box, enter a valid email address.Click or tap Edit to see other fields that you can update.At the top right of the screen, click Create flow, then Done.We will see this flow run when we walk through the scenario end-to-end. Now we’ll move on to the last task in this scenario—embedding a Power BI report into SharePoint.Task 8: Embed a Power BI report in SharePointThe last task in this scenario is to embed our Power BI report in the same SharePoint Online site that hosts our two lists. Power BI supports a variety of approaches to embedding, and has recently added integration directly into SharePoint pages for web and mobile views. With this type of embedding, Power BI embeds the report as a web part, provides appropriate access for users, and lets you click through from the embedded report to the report at . First, we’ll generate an embed link in Power BI, then use that link in a page that we create. For more information on embedding, see Embed with report web part in SharePoint Online (especially the Requirements section).Generate an embed link:Sign in to Power BI, then in the left navigation pane, click or tap the report name.Click or tap Embed in SharePoint Online.Copy the embed link from the dialog box to a file, then click Close. We will use the link after we create a SharePoint page.Embed the report:Sign in to SharePoint, then click or tap Site contents.You could just include a report on the team home page, but we’ll show you how to create a separate page for it also. Click or tap New, then Page.Enter a name for the page, like “Project Analysis”.Click or tap then Power BI.Click or tap Add report.In the right pane, copy the embed URL into the Power BI report link box. Set both Show Filter Pane and Show Navigation Pane to On.The report is now embedded in the page. Click Publish to make it available to anyone who can access the underlying report.Grant access to the report.If you are using Office 365 Groups as we recommend, list users who need access as members of the group workspace within the Power BI service. This ensures that users can view the contents of that group. For more information, see Creating groups in Power BI.That wraps up our work in Power BI for this scenario. You started by pulling data from our SharePoint lists into Power BI, and have now come full circle to embedding your Power BI report back into SharePoint. SummaryWe have covered a huge amount of ground in this paper, from building apps and flows, to creating reports and embedding them in SharePoint. We hope you’ve learned a lot and have enough exposure to how these technologies integrate, so that you can integrate apps, flows, and reports into SharePoint based on your own needs. Before we finish, we want to walk through the scenario end-to-end and see how all the parts work together. Step 1: Add a project to the Project Requests listIn the Project Requests list, click or tap All Items, then Project Requests app.Click Open, which opens the app in a new browser tab.In the app, click or tap to create a new item.Fill out the form with the following values:Title = “Mobile devices for design team”Approved = “Pending”Description = “The design team will now use Contoso-supplied devices”EstimatedDays = “30”ProjectType = “New hardware”RequestDate = “03/01/2017”Requestor = “Emily Braun”Click or tap , then close the browser tab.Go back to the Project Requests list, click or tap Project Requests app, then All Items.Verify the new entry in the list.Step 2: Approve the projectWhen you add the item in Step 1, the flow should run and send out an approval mail. Check the inbox of the approver’s email account. Click Approve. The flow runs another process, and you get feedback like the following directly in the email.Check the inbox of the requestor’s email account, and you should see an approval email.Verify the updated entry in the list.Step 3: Assign a manager to the projectFirst, let’s look at the Project Details list in SharePoint. The new project has a value of Unassigned in the PMAssigned column.In the SharePoint site, in the left navigation, click or tap Project Management app.On the first screen, click or tap Assign Manager.On the Assign Manager screen, you see the two unassigned projects from the list. Select the Mobile devices for design team project.In the Manager text box, enter “Joni Sherman”, then click OK.The change is applied to the list, and the gallery refreshes so only the remaining unassigned project is displayed.Close the app, and go back to the SharePoint list. You’ll see that the project entry is now updated with the project manager name. Step 4: Add time estimates for the projectClick or tap to go back to the first screen, then click or tap Update Details.On the View Projects screen, enter “Mobile” in the search box.Click for the Mobile devices for design team item.On the Update Details screen, set the following values:The Status field = “Not started”The ProjectedStartDate field = “3/6/2017” The ProjectedEndDate field = “3/24/2017”The ProjectedDays field = “15” Click or tap to apply the change to the SharePoint list.Close the app, and go back to the list. You’ll see that the project entry is now updated with the date and day changes. Step 5: Review report data for existing projects In SharePoint Online, click or tap Site contents, then Site Pages.Open the Project Analysis page that we created earlier.Review the variance visualization.As we noted when we created this visualization, there is a lot more variance for projects that were run by Irvin Sayers versus Joni Sherman. Drill into the visualization, and you see that much of the variance comes from two projects that took a lot longer than projected.Review the table that shows how long it takes for projects to go from approval to projected start date. As we noted when we created this visualization, the projects that Irvin Sayers is assigned to take longer to start with two projects taking much longer than the rest.Step 6: Respond to pending project delaysIn the Power BI service, click or tap the project-analysis dataset, then click or tap REFRESH NOW. The refresh triggers the alert we set up for pending projects.After the refresh is complete, the Notification Center at top right shows a new notification icon.This can take some time, so check back if you don’t see it right away.Open the Notification Center to see the details of the alert that fired.Check the inbox for the person who created the alert (Megan Bowen in our case).Check the inbox for the person you added in the data alerts flow (Allan DeYoung in our case).Now that you have information on pending projects, you can go back and approve any that have been waiting for your attention.That brings us to the conclusion of our end-to-end walkthrough and the paper itself. We encourage you to continue your journey at the following sites:PowerAppsMicrosoft FlowPower BISharePointMicrosoft Tech CommunityLet us know at mblythe@ if you have any feedback on this paper, suggestions for additions, or ideas for additional content that will help you work with the technologies covered in this paper. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download