Replaced PDF for Markdown files

build-tools/PowerApps_Build Tools_Lab/PowerPlatform_DevOps_Module0.md

@@ -0,0 +1,82 @@
+# Power Apps Lab
+## Module 0: Pre-Lab Setup and Review using Azure DevOps
+Last updated: February 15, 2021
+Authors: Per Mikkelsen, Shan McArthur, Evan Chaki, Amin Espinoza
+
+### Overview
+
+This hand-on lab will give you an opportunity to get hands on with the best practices to get your app
+into source control, generate a managed solution from Source (your build artifact) and finally deploy the
+app into another environment. You will need access to 3 Common Data Service environments
+(Development, Build & Production) along with Azure DevOps to automate deployments.
+
+### Pre-Lab Setup:
+
+You will need to create three environments in your demo or customer tenant. To do this follow these
+instructions:
+
+1. Login to a tenant that you have access to and that minimum 3GB available capacity which is required to create 3 environments.
+
+2. Go to [https://admin.powerplatform.microsoft.com/](https://admin.powerplatform.microsoft.com/), this will take you to the *admin center*.
+
+3. Select **environments** in the navigation area.
+
+![Environments](./assets/module0/img0.jpg)
+
+4. Select **+ New** to create your first new environment.
+
+![New environment](./assets/module0/img1.jpg)
+
+5. The first environment should be named **Your Name – dev**, set the region to **United States (default)**, set the Environment type to **Production** (if available) if not use **Trial**. Select the option to create a database for the new environment.
+
+![Creation](./assets/module0/img2.jpg)
+
+6. In next section to create a database you can select a language, and an URL, this URL has to be unique, also select the currency, and select **Yes** when prompted to deploy sample apps and data.
+
+![Database](./assets/module0/img3.jpg)
+
+7. Your development environment has been created, follow steps 4 – 6 above to create a second environment called **Your Name – build**, and then finally, create a third environment called **Your Name – prod** – NOTE the third environment can be a trial environment type.
+
+![Three environments](./assets/module0/img4.jpg)
+
+8. Now that you have the environments that we will need for this lab, it's time to go to Azure DevOps. Create a DevOps project by going to [https://dev.azure.com](https://dev.azure.com) and selecting **Sign into Azure DevOps**. Select **+ Create project**. 
+
+![New project](./assets/module0/img5.jpg)
+
+9. Create a new project name called **Your name - DevOps Project**, make it a Private project and select **Create**.
+
+![Project wizard](./assets/module0/img6.jpg)
+
+10. Your DevOps project has now been created, please note the URL on the top for your project and bookmark it or save it locally.
+
+![Project dashboard](./assets/module0/img7.jpg)
+
+11. You are now ready to begin the ALM Hands-on Lab.
+
+### ALM Hands-on Lab Overview
+
+During this lab you will use the account, login, and environments you created in the previous steps. You will get hands-on with the full set of Application Lifecycle Management (ALM) capabilities for the Power Platform. Learn how to use the key concepts that allow customers and partners to manage solutions and deploy them across environments. Additionally, get up to speed with the details of canvas apps and flows in solutions.
+
+1. Let's get familiar with the environments that you created (in the pre-lab) or were created for you.
+
+2. Go to [https://admin.powerplatform.microsoft.com/environments](https://admin.powerplatform.microsoft.com/environments) to view the environment you have access to.
+
+3. You will see your environments, one with dev in the name, one with build in the name and a third with prod in the name.
+
+![Three environments](./assets/module0/img4.jpg)
+
+4. We will use these environments as our primary environments during the lab. Your user will have the **System Administrator** Common Data Service role for all environments giving you full access to the environment.
+
+5. In a new tab open [https://make.powerapps.com](https://make.powerapps.com).
+
+![Power Apps](./assets/module0/img8.jpg)
+
+6. In the header, you will see a way to switch environments to move between your different environments.
+
+![Environments options](./assets/module0/img9.jpg)
+
+7. When you change to a new environment Power Apps.com will also change to show only content relevant to that environment. Both environments contain a Common Data Service database. This allows you to leverage the Common Data Service solution infrastructure to move app, entities, code and other resources from one environment to another.
+
+8. Select **Solutions** in the navigation.
+
+9. Solutions are how customizers and developers author, package, and maintain units of software that extend Dataverse. Customizers and developers distribute solutions so that organizations can use Dataverse to install and uninstall the app(s) defined in the solution. In the next Module you will learn how to create a new solution.

build-tools/PowerApps_Build Tools_Lab/PowerPlatform_DevOps_Module1.md

@@ -0,0 +1,77 @@
+# Power Apps Hands-on Lab
+## Module 1: Building Basic Model-driven Common Data Service Application for Deployment Using Azure DevOps
+Last updated: February 15, 2021
+Authors: Per Mikkelsen, Shan McArthur, Evan Chaki, Amin Espinoza
+
+In this lab you will be creating a basic Model-driven Dataverse application to use with Module 2 of the lab to automate the application lifecycle management (ALM) of the application.
+
+1. Navigate to [https://make.powerapps.com](https://make.powerapps.com) and sign in with your credentials. Click the environment selector dropdown the header and select your development environment.
+
+![Environments](./assets/module1/img0.jpg)
+
+2. Click the **Solutions** area in the left navigation then click the **New Solution** button to create a new solution.
+
+![Solutions](./assets/module1/img1.jpg)
+
+3. In the side panel that appears, enter a name for the application and click the dropdown for the publisher and click the **Add Publisher** option. 
+**Note**: The solution publisher specifies who developed the app. For this reason, you should create a solution publisher name that's meaningful. Furthermore, the solution publisher includes a prefix, which helps you distinguish system components or components introduced by others and is also a mechanism to help avoid naming collisions. This allows for solutions from different publishers to be installed in an environment with minimal conflicts.
+
+![Publisher](./assets/module1/img2.jpg)
+
+4. A new window will pop up. If a window does not pop up, check your popup blocker settings. For the purpose of this lab, enter your **ALMLab** for the display name, name and prefix and click **Save and Close**.
+
+![New publisher](./assets/module1/img3.jpg)
+
+5. On the new solution panel, select the publisher that you just created, give the application a version number, and click **Create** to create a new unmanaged solution in the environment.
+
+![New solution](./assets/module1/img4.jpg)
+
+6. In the solutions list, select the solution you just created and click the **Edit** button.
+
+![Edit](./assets/module1/img5.jpg)
+
+7. Your new solution will be empty, and you need to add components to it. In this lab we will create a custom entity. Click the **New** dropdown from the top navigation and select Table.
+
+![Table](./assets/module1/img6.jpg)
+
+8. Enter a display name and plural name. The system will fill out the table name and other fields for you. Click **create** to create the table.
+
+![New table](./assets/module1/img7.jpg)
+
+9. Once your table is created, click the solution name again to go back to the solution view to add another component.
+
+10. Click the New **dropdown**, then App, and **Model-driven app**.
+
+![New app](./assets/module1/img8.jpg)
+
+11. Enter an application name and click the **Done** button.
+
+![Create app](./assets/module1/img9.jpg)
+
+12. In the application designer, click the **Site Map** to edit it.
+
+![Site map](./assets/module1/img10.jpg)
+
+13. In the site map editor, select the **New Subarea** to get its current properties.
+
+![Site map](./assets/module1/img11.jpg)
+
+14. Select the Entity dropdown and select your custom table to add to the sitemap.
+
+![Custom table](./assets/module1/img12.jpg)
+
+15. Click **Save**, then **Publish**, then **Save and Close** to go back to the application designer.
+
+![Save](./assets/module1/img13.jpg)
+
+16. Click **Save** then Validate to validate the application.
+
+![Validate](./assets/module1/img14.jpg)
+
+17. You should see one warning. View the warning, then click **Publish** then **Play**.
+
+![Warning](./assets/module1/img15.jpg)
+
+18. This will take you to the application so that you can see how it looks. You can use the application and close the tab when you are satisfied.
+
+![App](./assets/module1/img16.jpg)