PowerApps Jumpstart Sandy Ussia #SPSSTHLM, Sept 1, 2018

Thank you sponsors!

SPS Stockholm #SPSSTHLM Powerapps jumpstart SPS Stockholm #SPSSTHLM

SharePoint since 2007 Lightning Tools Global Partner Manager Digital Nomad SandyU.com @SandyU SandyUssia sandy@sandyu.com

Why powerapps? Objective of this session Work where you work Designed for mobile devices (but also browser) Over 200 Connectors available No/Low code Successor to InfoPath for SharePoint forms Have you tried PowerApps yet? Objective of this session Show you around PowerApps, give you some ideas of how you can go further

getting started https://powerapps.Microsoft.com Create from data (e.g. SharePoint list) – automatic 3-screen app Create from one of the templates, and learn from it Customize forms in a SharePoint list NEW! Model-driven apps … or start from blank

Create from data (demo) Automatically gives you a 3-screen “working” app, but you’ll likely want to make a few initial changes. Edit the gallery layout - default is (now) “Title, Subtitle, and body”, but perhaps the fields need to be rearranged Edit the fields being displayed (on each screen) NOTE: An app created based on a SharePoint list will show up as an available View for that list, to users with whom the app has been shared.

customize sharepoint forms (demo) Automatically gives you a single Form screen with New/Edit/View modes Change the screen size and orientation under App Settings (Landscape/Large makes a nice SharePoint list pane). Best to change this first before laying out fields. Use the Data pane to select which fields to display. Use Snap to columns and Horizontal/Vertical Layout to make easy layout changes. Each field is displayed on a “card”, which can be unlocked to make changes. Use the Visible property to conditionally display a field (example: Parent.DisplayMode=“view”). Set DisplayMode to DisplayMode.View to make a field non-editable (view-only). The SharePointIntegration object is what ties it to your SharePoint list. Use List Settings > Form Settings to switch back to the standard SharePoint form. Customized forms are not currently available to external (guest) users. NOTE: These “apps” are not available in the list of Apps – they only work within the context of the SharePoint list, in the browser or in the SharePoint mobile app. However, admins can see a list of PowerApps-customized forms in the Admin Center. SharePoint form customization reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/customize-list-form

canvas tour (demo/app)

controls (demo/app) A control is any object you add to the canvas Values are generally pulled, not pushed. So enter a formula in the control you wish to affect. Exception: “On” properties (OnSelect, OnStart, etc) Properties of one control can be referenced in another control. Example: txtNameInput.Text Also, a control can reference its own properties. It’s a good practice to rename controls meaningfully right after creating them. (Renaming later also works.) Example: btnSubmit Controls documentation: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/reference-properties

data (demo/App) Data source: connection to data. Not only lists of data, but also includes things like O365 Users or Bing maps. Access connections via the View menu, or from within a control such as a Gallery. Gallery and Data Table controls display data sets Collection: temporary storage of data in an array (table)

variables Set (global scope): Set(YourVariableName, SomeValue) UpdateContext (screen scope): UpdateContext({YourVariableName: SomeValue}) Variable reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/working-with-variables

important basic concepts Remember that a “button” can also be a Label or an Image. You can access all properties of a control either in the right pane, or in the properties dropdown. Select multiple controls to quickly set common properties. Ctrl-C/Ctrl-V to copy/paste controls. Group controls to display/hide them together using the Visible property. Formulas are in the controls which they affect, not where you might enter data. For example, the Search box in a pre-built app is referred to in the Gallery where you want the results displayed, so the formula (what to search) goes in the Items property of the Gallery. Values are pulled, not pushed. Intellisense, colors, and tooltips are your friends when writing formulas. Complex fields (such as O365 users or SharePoint lookup columns) usually require a modifier in a formula (e.g. Brewery.Value or Office365Users.UserProfile(aUserEmail).JobTitle)

references Documentation for canvas apps List of Connectors PowerApps Community forums New PowerApps User Group! Microsoft Guided Learning (series of brief videos) Audrie Gordon’s YouTube channel Community resources: Shane Young, Dan Christian, Paul Culmsee, Laura Rogers, me…

Microsoft SharePoint Server 2013 Thank you! Please visit our sponsors who made this day possible! Rate this session with the event app (and win a prize) Need to update graphic to survey http://rate.spssthlm.org © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Thank you sponsors!