When Microsoft Dynamics 365 was announced a few weeks ago, the Common Data Model and other Microsoft productivity services such as PowerApps and Microsoft Flow were a significant part of this, along with the unified offering of Dynamics CRM and Dynamics ERP cloud services under this umbrella. The solution stack diagram below for Dynamics 365 depicts the positioning of these various elements in Dynamics 365. In my earlier post I mentioned about the release of the public preview of the Common Data Model last week. Now that the public preview of the Common Data Model is available, let us try to make sense of these together and see what are the possibilities using the CDM and Microsoft PowerApps. In today’s post, we will create a simple example mobile app using Microsoft PowerApps and the Common Data Model database. Log in to Microsoft PowerApps at the URL https://powerapps.microsoft.com. You can use the PowerApps web version to create your apps. But the best way to do this is to download the app from Windows store . In this post, I will use the windows store app to create this sample mobile app. Launch PowerApps and click New tab to select the data source. While you can use various data sources such as Dynamics CRM online, excel file stored in the cloud, online storage such as OneDrive or Google Drive, in this case we will use the Common Data Model as the data source for this app. On the next screen, select the entity that you want to use in this app and click Connect button. For this sample app, we will use the Sales Order entity and build a simple app to interact with Sales orders (Simple actions such as view sales orders, edit or even create a new order). At this point, PowerApps will consume the Sales Order entity data and create the sample app with some default screens automatically, which you can adjust and change to make it look the way you want it. The auto creation feature comes in handy, as you do not need to create the app from scratch. Now that the default screens of the app are created, let us try to edit those a little bit to make them look more complete. The first screen is a Sales Order overview screen that shows the list of sales orders. Rename the screen to call it as “Sales Orders Overview”. Next, lets establish the links to some of the data fields to show the sales order overview data. In this case, we will show the customer name, Sales order number, order status and the sales order total amount. To do this, select each data field and select the data field for each field on the right hand panel. You will now notice that the first overview screen of the app looks more complete with meaningful data and you also have basic actions such as searching a sales order, or even sorting them. You can also select a different layout for this screen at this point if you want by selecting from various readily available templates. Let us now move on to the next screen, which will load up when user select or taps on a specific sales order record on the first screen. Let us call the next screen as the Sales order details screen. Follow the same approach to make edits to this screen. For example, we will add a few data fields and change the layout a little bit. In this screen, you can click on the “eye” mark to add or remove fields and then click Advanced option to chose data fields relation, or even rename a specific data field. For this demonstration, I have added simple data fields such as Order ID, Name, address, payment terms, shipping method, order date and tax, discount amounts of the order. At the end of this your screen should look something like below. You can also change the layout of this page, like you did for the first screen. Moving on to the 3rd screen of the app, let us make it the Edit screen for the sales order. When user clicks on the Edit button on screen 2, this screen will load up. Follow the same instructions above to complete the design of this page. You screen should look something like below. You can then explore the various tabs on the top to change different aspects of the app. For example you can add a new screen, change the color and theme of the app, add a new data source(such as the Sale Order line table if you want show order lines on this app), add a background image for the app, or even add new controls to the app such as a new button, a text field, charts and more. Now that all the screens we intended are designed, let us preview the app by clicking the preview button and you will notice that you can interact with the app in various ways. For example on the first screen when we select a specific sales order record, it will navigate to the details page. (Note: I have changed the theme of the app before previewing it.) Finally we will save the app (you can save it in the cloud or in your local computer) and then share it for consumption by others. Notice that you can specify with whom you want to share this app and what level of permission you want to give them while sharing the app. Below screenshot shows how this mobile app looked on my smartphone after I shared it and launched it on my Android phone. This was just a very simple demonstration of the possibilities and what you can do with the Common Data Model and productivity tools such as PowerApps or Microsoft flow. The CDM is in preview now, but when it releases this fall, you will see a lot more data entities and much more capabilities of designing powerful business apps in the cloud for your organization.