PowerApps – Intro
What is PowerApps? PowerApps is a service for generating cross platform (iOS, Android, Windows Store) applications. It allows connectivity to different systems, comes up with cloud IDE and a cloud admin interface that allows users to publish apps targeting whatever platform you need. The IDE is called PowerApps Studio and can be downloaded from Windows Store locally on your machine or it can be used as a web application. I designed the app detailed below using the web application.
Most importantly, just like the other power tools, PowerBI and MS Flow, PowerApps is accessible not only to professional developers, but also business analysts, junior developers, or expert users in any company. I wrote this app without any code inside PowerApps Studio, just a few Excel functions invoked sporadically.
The quick PowerApps app I built required:
- a PowerApps license. I got my free license here.
- a NAV container hosted on Azure. You could build yours easily, some help here.
The app will get from the Azure Business Central container the list of items via Item List page exposed as web service, and will present on the first screen the Item No. and Description for all items. App user can then advance into the details screen for each item. Here, if the Quantity is low the user can advance on a third screen where he can generate a purchase invoice for the desired quantity for the item and vendor selected. The result is that in Business Central the app will generate via a second web service a purchase invoice for the item, the vendor selected and the quantity entered.
There are two main parts to create your app:
- Create app connector
- Design app
1. Create app connectors
To create a Business Central connector go to the File menu in the PowerApps Studio and choose Connections:
The connector to the Azure BC Container instance looks like this:
Once the connector is set we can access all web services exposed in Business Central Azure Container.
2. Design PowerApps app
The PowerApps Studio comes with 3 main regions:
- Left Side is where you work with the screens. In this simple app I have 4 screens: Master, Detail, Order and Confirm.
- The center belongs to the canvas where you drop your controls
- Right side is occupied by the Data Source (if any) and the properties of the current control you selected on the canvas
MasterScreen consists of a Galleria control (GalleriaItems) which contains a list of items retrieved via Items web service Data Source. You will see later that this web service is Page 31 exposed as web service in Business Central Azure Container.
OnSelect event for the Forward button has Navigate(screen,effect) function behind to advance to a certain screen in your app.
The second screen, DetailScreen displays a bit more fields from Items web service.
If the inventory is low, the app user can decide to order more by clicking on “Order more” button:
Once the user enters the desired quantity to be included on a Business Central Purchase Invoice the app will create a POST request to a new ODATA web service data source (OrderItemVendorWS) and ultimately generate the purchase invoice with one purchase line.
Let’s see the app:
And, in Business Central, the new purchase invoice:
This is what was needed on the PowerApps side, but additionally, I needed to plug a few new things in Business Central.
Business Central Container changes
First, create a new AL project, and point Visual Studio Code to the azure container:
- Items service will support MasterScreen and DetailScreen
- OrderItemVendorWS will support OrderScreen.
Page 50100 “PurchaseItemList” is a new page based on a new Table 50100 PurchaseItem:
Table 50100 PurchaseItem:
Page 50100 PurchaseItemList:
The Purchase Invoice is generated during OnInsert trigger on the new table:
Creating an app with PowerApps assumes 3 tasks:
- the app backend, the connectors to your apps
- the app design, done in PowerApps Studio
- Publishing and Management tasks
PowerApps comes with versioning and management capabilities of a few environments (E.g. Dev, QA, Prod). Once your app has been tested by PowerApps app users, you could export it from QA and import it in Prod and distributed it from there. Select Office and Dynamics 365 plans will allow you to generate and manage these environments.
More specifically, if you go to web.powerapps.com and click on Solutions you will be able to follow (with the right license) Create a new environment link.
Some useful links:
Hi, nice post. What kind of code (post command) is behind the button Generate Post Invoice?
Thanks for sharing. I have the following idea related to PowerApps/CDS and BC.
1. Create CDS Entities that taking the data from BC using Odata
2. Create PowerApps based on CDS entities on point 1
3. User will key-in information in PowerApps
4. Push data back from CDS to BC. (or BC to pull the data from CDS)
I am wondering how point 4 will works without Power Automate. Do you have an idea about that?