2327179

tapanm-MSFT · tapanm-MSFT · commit 510e8e896bf2 · 2021-07-12T15:38:53.000-07:00
diff --git a/powerapps-docs/maker/TOC.yml b/powerapps-docs/maker/TOC.yml
@@ -2264,6 +2264,8 @@
                   href: ../teams/inspection-architecture.md
                 - name: Customize Inspection sample app
                   href: ../teams/customize-inspections.md
+                - name: Add hierarchy inspection ___location
+                  href: ../teams/inspections-hierarchy-locations.md
         - name: Issue reporting
           items:
             - name: Issue reporting
diff --git a/powerapps-docs/teams/inspections-hierarchy-locations.md b/powerapps-docs/teams/inspections-hierarchy-locations.md
@@ -1,149 +1,134 @@
 ---
-title: Add hierarchy to ___location of Inspection
-description: Learn about how the Inspection sample apps can be extended to add ___location of inspection
+title: Add hierarchy to inspection ___location
+description: Learn about how to add hierarchy to inspection locations in Inspections sample app.
 author: sbahl10
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 06/15/2021
+ms.date: 07/12/2021
 ms.author: v-shrutibahl
 ms.reviewer: tapanm
 contributors:
-- v-ljoel
+  - joel-lindstrom
+  - navjotm
+  - tapanm-msft
+  - sbahl10
 ---
 
-# Inspections App – Add hierarchy to ___location of inspection
+# Add hierarchy to inspection ___location
 
-The Inspections Power Apps template allows users to create and perform inspections in the app. There are three apps, one per persona to perform,
-manage, and review Inspections. The three apps are – Inspections, Manage Inspections and Review Inspections.
+The Inspections sample app allows users to create and perform inspections in the app. There are three apps, one per persona to perform, manage, and review Inspections. The three apps are&mdash;Inspections, Manage Inspections and Review Inspections.
 
-By default the Inspection app is designed for a single store. But what if you perform inspections on multiple stores? You will want to add a table for stores to the app and let the user select the store in which they are performing inspections so that you can track at which store the inspection was performed.
+By default, the Inspections app is designed for a single store. But what if you perform inspections on multiple stores? You'll want to add a table for stores to the app and let the user select the store in which they are performing inspections so that you can track at which store the inspection was performed.
 
-In this topic we will learn how to update the app to add a hierarchy of stores so that inspections can be performed for different stores.
+In this article, we'll learn how to update the app to add a hierarchy of stores so that inspections can be performed for different stores.
 
 ## Prerequisites
 
-To complete this lesson, we would need the ability to login into Microsoft Teams which will be available as part of select Microsoft 365 subscriptions and will also need to have the Inspections Power Apps template for Microsoft Teams installed. This app can be installed from aka.ms/TeamsInspection.
+To complete this lesson, we'd need the ability to login into Microsoft Teams which will be available as part of select Microsoft 365 subscriptions, and will also need to have the Inspections sample app for Teams installed. This app can be installed from <https://aka.ms/TeamsInspection>.
 
 ## Edit the Inspections app
 
-1.  Login into Teams and right click Power Apps from the left menu and select **Pop out app**.
-    
-2.  Select Build from the top ribbon.
+1. Login into Teams, and right-click on Power Apps app from the left-pane, and select **Pop out app**.
 
-3.  Select the Team in which the Inspections app is installed.
+1. Select **Build** from the top ribbon.
 
-4.  Select Inspections to open the app in the editor.
+1. Select the team in which the Inspections app is installed.
 
-5.  The Inspections app opens.
+1. Select Inspections to open the app in Power Apps Studio.
 
 ### Add a new table called Store
 
-1.  Select **Data** from the left navigation menu.
+1. Select **Data** from the left-pane.
 
-2.  Select **+Add data**.
+1. Select **+ Add data**.
 
-3.  Select the **+Create new table**.
+1. Select the **+ Create new table**.
 
-4.  Enter table name Store and select **Create**.
+1. Enter table name Store and select **Create**.
 
-5.  Select the **Add Column** button to add a new column.
+1. Select the **Add Column** button to add a new column.
 
-6.  Enter column name = Store Number and select **Create** – the column gets added.
+1. Enter column name as "Store Number", and select **Create**.
 
-7.  Add a few records of data in the table and select **Close.**
+1. Add a few sample records in the table, and select **Close.**
 
-![Store Table](media/extend-inspections-add-hierarchy-to-locations/store-table.png "Store Table")
+    ![Store Table](media/extend-inspections-add-hierarchy-to-locations/store-table.png "Store Table")
 
 ### Add a column to capture Store in the Area Inspections table
 
-1.  Select **Data** from the left navigation menu.
+1. Select **Data** from the left navigation menu.
 
-2.  Locate the Area Inspections table and hit on the three dots.
+1. Locate the **Area Inspections** table and hit on the three dots.
 
-3.  Select **Edit Data**.
+1. Select **Edit data**.
 
-4.  The Area Inspections table opens.
+1. Select **Add Column**, and enter the table name as "Store", type as "Lookup", and related table as "Store".
 
-5.  Select **Add Column**, enter the Table name = Store, Type = Lookup, Related Table = Store.
-    
-6.  Select **Create**.
+1. Select **Create**.
 
-7.  The column gets added.
-
-8.  Select the **Close** button to close the table.
+1. Select **Close**.
 
 ### Add a new screen with a Gallery of Stores
 
-1. Select the Tree view from the left navigation menu.
-
-2. Select **+New** screen from the tree view.
-
-3. Select Blank layout.
-
-4. The new screen gets added.
+1. Select the Tree view from the left-pane.
 
-5. Rename the screen to **StoreSelectionScreen**.
+1. Select **+ New** screen from the tree view.
 
-6. Update the Fill property to **gblAppStyles.Background.Fill**.
+1. Select blank layout.
 
-7. Select the **+Insert** button to add a Gallery to the new screen.
+1. Rename the screen to "StoreSelectionScreen".
 
-8. Select Stores as the data source.
+1. Update the **Fill** property to `gblAppStyles.Background.Fill`.
 
-9. Gallery gets added to the new screen.
+1. Select **+ Insert** to add a gallery to the new screen.
 
-10. Rename the gallery to **StoresGallery**.
+1. Select **Stores** as the data source.
 
-11. Update Template Size to **108**.
+1. Rename the gallery to "StoresGallery".
 
-12. Update FontSize of Label Title4 to **20**.
+1. Set the following properties for the gallery **StoresGallery**.
 
-13. Set Height of Label Title4 to **45**.
+    | Property | Value |
+    | - | - |
+    | Template size | 108 |
+    | Font size | 20 |
+    | Height for Title4 | 45 |
+    | Font size for label Subtitle4 | 18 |
+    | Height for label Subtitle4 | 45 |
 
-14. Update FontSize of Label Subtitle4 to **18**.
+1. Go to the **Items** screen, and copy the **Back** button from the top of the screen.
 
-15. Set Height of Label Subtitle4 to **45**.
+1. Paste the copied button on the new screen.
 
-16. Navigate to Items screen and copy the Back button from the top of the screen.
+1. Repeat the previous steps to copy the label **lblIndividualAreasHeader** from Items screen that reads the text as ___location to the new screen.
 
-17. Go back to the New screen and paste the Back button copied in the previous step.
+1. Set **Y** property of the label to `btnBackToHome_1.Y+btnBackToHome_1.Height`.
 
-18. Now, navigate again to the Items screen and copy the label lblIndividualAreasHeader that reads the text as Location.
+1. Set the following properties of the gallery **StoresGallery**.
 
-19. Go back to the New screen and paste the label copied in the previous step.
+    | Property | Value |
+    | - | - |
+    | Y | `btnBackToHome_1.Height+lblIndividualAreasHeader_1.Height` |
+    | Height `Parent.Height-btnBackToHome_1.Height- lblIndividualAreasHeader_1.Height` |
+    | OnSelect | `Set(gblSelectedStore,ThisItem);Navigate('Items Screen')` |
 
-20.  Set the following properties of the label
-     - Y = **btnBackToHome\_1.Y+btnBackToHome_1.Height**
-     
-21.  Set the following properties of the gallery StoresGallery
+1. Go to the Items, select the **Back to home** button on top, and update the following button properties.
 
-     - Y = **btnBackToHome\_1.Height+lblIndividualAreasHeader_1.Height**
+    | Property | Value |
+    | - | - |
+    | OnSelect | `Navigate(StoreSelectionScreen, ScreenTransition.Fade)` |
+    | Text | `"Back to Store Selection"` |
 
-     - Height = **Parent.Height-btnBackToHome\_1.Height- lblIndividualAreasHeader_1.Height**
-     
-     - OnSelect = **Set(gblSelectedStore,ThisItem);Navigate('Items Screen')**
-     
-22. Navigate to the Items Screen and select the **Back to home** button on top.
+1. Go to **Checklist Steps** screen.
 
-23.  Update the following properties of that button
+1. Select the **OnSelect** property of the screen, and update the patch function for updating the **Area Inspections** app to add the store value in the formula.
 
-     - OnSelect = **Navigate(StoreSelectionScreen, ScreenTransition.Fade)**
-
-     - Text = **"Back to Store Selection"**
-     
-24. Navigate to Checklist Steps Screen.
-
-25. Select the OnSelect property of the screen.
-
-26. Update the Patch function for updating the Area Inspections app to add the Store value in the formula – 
-
-    ```
+    ```powerapps-dot
     , Store: gblSelectedStore
     ```
 
-
-![Add Store to the Patch function](media/extend-inspections-add-hierarchy-to-locations/add-store-to-patch.png "Add Store to the Patch function")
+    ![Add Store to the Patch function](media/extend-inspections-add-hierarchy-to-locations/add-store-to-patch.png "Add Store to the Patch function")
 
 ### Update the Welcome Screen navigation
 
@@ -167,7 +152,7 @@ To complete this lesson, we would need the ability to login into Microsoft Teams
 
 ### Publish the Inspections app
 
-1.  All the changes to the Inspection app are completed.
+1.  All the changes to the Inspections app are completed.
 
 2.  The app can now be published by selecting the Publish to Teams button on the top right.
 
@@ -341,7 +326,7 @@ Days
 
 ## Test the app
 
-1.  Open the Inspection App in the team in which it is installed.
+1.  Open the Inspections app in the team in which it is installed.
 
 2.  The app loads.
 
@@ -380,3 +365,13 @@ Days
 19.  The screen displays the Store name before the Submitted by as shown in the screenshot below.
 
 ![Store showing on Location screen](media/extend-inspections-add-hierarchy-to-locations/test-result-store-on-___location-screen.png "Store showing on Location screen")
+
+### See also
+
+- [Understand Inspection sample apps architecture](inspection-architecture.md)
+- [Customize Inspection sample app](customize-inspections.md)
+- [Customize sample apps](customize-sample-apps.md)
+- [Sample apps FAQs](sample-apps-faqs.md)
+- [Use sample apps from the Teams store](use-sample-apps-from-teams-store.md)
+
+[!INCLUDE[footer-include](../includes/footer-banner.md)]
