Merge branch 'master' into pehecke-webapi-sample-update

Author: phecke

powerapps-docs/developer/common-data-service/TOC.yml

@@ -27,6 +27,8 @@
       href: use-fetchxml-left-outer-join-query-records-not-in.md
     - name: Page large result sets with FetchXML
       href: org-service/page-large-result-sets-with-fetchxml.md
+    - name: Paging behaviors and ordering
+      href: org-service/paging-behaviors-and-ordering.md
     - name: Use column comparison in queries
       href: column-comparison.md
   - name: "Use SQL to query data (Preview)"

powerapps-docs/developer/common-data-service/org-service/page-large-result-sets-with-fetchxml.md

@@ -108,7 +108,9 @@ while (true)
 }
 ```
 
-### See also  
+### See also
+
+ [Paging behaviors and ordering](paging-behaviors-and-ordering.md)  
  [Sample: Use FetchXML with a Paging Cookie](samples/use-fetchxml-paging-cookie.md)   
  [Building Queries with FetchXML](/dynamics365/customer-engagement/developer/org-service/build-queries-fetchxml)   
  [Fiscal date and older than datetime query operators in FetchXML](../use-fetchxml-fiscal-date-older-datetime-query-operators.md)   

powerapps-docs/developer/common-data-service/org-service/paging-behaviors-and-ordering.md

@@ -0,0 +1,179 @@
+---
+title: "Paging behaviors and ordering (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "Learn about the different paging behaviors for FetchXML queries and how you can write queries to get the desired paging results." # 115-145 characters including spaces. This abstract displays in the search result.
+ms.custom: ""
+ms.date: 7/20/2020
+ms.reviewer: "pehecke"
+ms.service: powerapps
+ms.topic: "article"
+author: "NHelgren" # GitHub ID
+ms.author: "nhelgren" # MSFT alias of Microsoft employees only
+manager: "mayadu" # MSFT alias of manager or PM counterpart
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+
+# Paging behaviors and ordering
+
+When querying data using FetchXML, paging query results can make viewing large
+volumes of information easier. It is important when using paging to include
+ordering parameters as well. Without proper ordering, paging requests for the
+“next 50” records can result in retrieving the same records across multiple
+pages making reviews and edits much more difficult. Proper page ordering
+requires including unique values to help identify which records are included in
+a page.
+
+## Legacy paging
+
+Legacy paging within the Common Data Service loads all the results of the query
+up to the current page into memory on the server, selects the number of records
+that are needed for the page, and then ignores the rest. This has benefits such
+as quick back/forward paging through the data or skipping to a specific page,
+but it also has restrictions such as a 50K row limit, performance issues with
+large complex queries, and arbitrarily sorted distinct query results.
+
+## Ordering with a paging cookie
+
+When paging with ordering, a cache of the previous page’s results is stored in a
+paging cookie. This is used to calculate what the next page of data should
+display.
+
+If a user does not specify any “order by” parameters, the system will
+automatically insert “order by "\<\<entity name\>\>".\<\<entityId\>\> asc” to
+provide some basic ordering. Depending on the data that is being queried, this
+may result in inadequate and unexpected results as a single system user can be
+associated with multiple records within any query.
+
+If distinct FetchXML queries are being used, the system will not add any
+additional ordering due to potential impacts to the data returned. In these
+cases, users will have to add at least a single ordering value for a more
+consistent paging experience.
+
+> [!NOTE]
+> Paging using FetchXML for Common Data Service is dynamic. The page a
+> record appears on is determined at the time that each page is rendered. If 1000
+> records are being displayed 50 to a page, the first 50 records are displayed as
+> page one. When page two is requested, the system determines what the next 50
+> records should be at the time of request. Because of this, it would not be
+> possible to use the new paging functionality for back paging. Legacy behavior is
+> used for back paging which will have reduced performance and any returns after
+> page 500 cannot be “paged back” due to legacy limitations. 
+
+### Why ordering is important
+
+If a query is run to retrieve all records with a state of “Open” this could
+result in 1000 returns. When paging from page one to page two, there is no way
+for the system to know which orders to display on page two because all of the
+records have the same state. The paging of these records will not be efficient
+or consistent.
+
+Providing an “order by” value gives the paging cookie the ability to order the
+data by an additional value and recognize the last record in a page based on the
+values provided.
+
+#### Example 1
+
+A query is created to get all records with a state of ‘Open’, include the status
+for every record, and show three records per page. The query is then ordered by
+status. The query result would page as shown in the following table:
+
+| State | Status | Page      |
+|-----------|------------|---------------|
+| Open      | Active     | 1             |
+| Open      | Active     | 1             |
+| Open      | Active     | End of page 1 |
+| Open      | Active     |               |
+| Open      | Active     |               |
+| Open      | Inactive   |               |
+| Open      | Inactive   |               |
+
+The paging cookie will save information about the last record on the page, but
+when it’s time to get page two in this example, there is no unique identifier to
+ensure that the next page populated uses the unviewed records or include the
+first two records that were on page one.
+
+To solve this problem, queries should include “order by” columns that have
+unique values. It is possible to use multiple “order by” values. Below is a
+better way to order data for this query:
+
+#### Example 2
+
+A query is created to get all records of a state of ‘Open’, any status, include
+the Case IDs, and show three records per page. It orders by status and by Case
+ID (a unique identifier) which will order in ascending order. The query result
+would page the results as shown below:
+
+| State | Status | Case ID | Page      |
+|-----------|------------|-------------|---------------|
+| Open      | Active     | Case-0010   | 1             |
+| Open      | Active     | Case-0021   | 1             |
+| Open      | Active     | Case-0032   | End of Page 1 |
+| Open      | Active     | Case-0034   |               |
+| Open      | Active     | Case-0070   |               |
+| Open      | Inactive   | Case-0015   |               |
+| Open      | Inactive   | Case-0047   |               |
+
+The query results are first ordered by the Status, and then ordered by the Case
+ID in ascending order. When page two is generated, the result would be as shown
+below:
+
+| State | Status | Case ID | Page      |
+|-----------|------------|-------------|---------------|
+| Open      | Active     | Case-0010   |               |
+| Open      | Active     | Case-0021   |               |
+| Open      | Active     | Case-0032   | End of Page 1 |
+| Open      | Active     | Case-0034   | 2             |
+| Open      | Active     | Case-0070   | 2             |
+| Open      | Inactive   | Case-0015   |               |
+| Open      | Inactive   | Case-0047   |               |
+
+When generating page two of this query set, the cookie will have Case-0032
+stored as the last record in the first page, so page two will pick up at the
+next record in the set after that record. This will allow for more consistent
+results.
+
+### Ordering suggestions
+
+Listed below are some suggestions for improving ordering of paging results, along with some areas to avoid.
+
+#### Best ordering
+
+- Always include a column that has a unique identifier (i.e., entity ID
+  columns, auto-number columns, user/contact IDs)
+
+#### Good ordering
+
+- Include multiple fields that will most likely result in unique combinations:
+  - First name + last name + email address
+  - Full name + email address
+  - Email address + company name
+
+#### Poor ordering
+
+- Orders that do not include unique identifiers
+
+- Orders that have single or multiple fields that are not likely to provide
+  uniqueness such as:
+  - Status and state
+  - Option sets or booleans
+  - Name values by themselves (i.e., last only, first only, company name
+    only)
+  - Text fields like titles, descriptions, multi-line text
+  - Non unique number fields
+
+### Ordering and multiple entity queries
+
+Sometimes data is needed that spans multiple entities and must be queried with a
+table JOIN. In these cases, ordering can be included for both entities in the
+query. Make sure to use at least one column with a unique ID per entity to
+ensure the paging provides the best results. However, the query will be
+downgraded to legacy paging, where no paging cookie will be returned, in these
+cases due to limitations of the N:1 relationship structure that could result in
+missing data.
+
+### See Also
+
+[Page large result sets with FetchXML](page-large-result-sets-with-fetchxml.md)

powerapps-docs/maker/TOC.yml

@@ -1746,6 +1746,22 @@
       href: ../sample-apps/crisis-financial-impact-tracker/use-mobile-app.md
     - name: Use dashboards
       href: ../sample-apps/crisis-financial-impact-tracker/configure-dashboards.md
+  - name: Return to the Workplace
+    items:
+    - name: Overview
+      href: ../sample-apps/return-to-workplace/overview.md
+    - name: Deploy the solution
+      href: ../sample-apps/return-to-workplace/deploy.md   
+    - name: Configure the solution
+      href: ../sample-apps/return-to-workplace/configure.md
+    - name: Location Readiness dashboard
+      href: ../sample-apps/return-to-workplace/dashboard-for-executive-leadership.md
+    - name: Facility Safety Management app
+      href: ../sample-apps/return-to-workplace/app-for-facility-manager.md
+    - name: Workplace Care Management app
+      href: ../sample-apps/return-to-workplace/app-for-health-and-safety-lead.md
+    - name: Employee Return to the Workplace app
+      href: ../sample-apps/return-to-workplace/app-for-employee.md
 - name: Learn from others
   items:
   - name: Blog

powerapps-docs/maker/canvas-apps/common-issues-and-resolutions.md

@@ -18,6 +18,9 @@ search.app:
 
 This article lists some common issues that you might encounter while using Power Apps. Where applicable, workarounds are provided.
 
+1. **Connection.Connected returns the wrong value during OnStart in Power Apps for Windows** (July 21, 2020)
+   While offline, **Connection.Connected** may wrongly return **true** immediately after starting an app in the Windows app. As a workaround, delay when the logic depending on it is executed by using a **Timer** control. 
+   
 1. **Black box covering part of embedded canvas app** (June 11, 2020)
    When using embedded canvas apps such as SharePoint forms, SharePoint web parts, and model driven forms, users many see a black box when scrolling covering part of the app. This issue happens with chromium based browsers starting with version 83. There is not a workaround at this time. The team is actively investigating to find a fix and workaround. **A workaround in Power Apps was deployed in the week of 6/21/2020. In addition, the issue is fixed for Microsoft Edge based on Chromium with version 85.**
 

powerapps-docs/maker/portals/media/maker-anatomy.png

@@ -0,0 +1,101 @@
+---
+title: Use the Employee Return to the Workplace app
+description: Provides information for employees to track their symptoms and determine whether they're eligible to enter into a facility.
+author: wbakker
+ms.service: powerapps
+ms.topic: conceptual
+ms.custom: 
+ms.date: 07/21/2020
+ms.author: garybird
+ms.reviewer: kvivek
+---
+
+# Use the Employee Return to the Workplace app
+
+This article provides step-by-step instructions about how to use the Employee Return to the Workplace app. You can check in, answer questions to determine whether you're eligible to enter a facility, and say how you feel about returning to the workplace.
+
+## Prerequisites
+
+- Download [Power Apps Mobile](https://powerapps.microsoft.com/downloads):
+
+  - For Apple devices with iOS, such as iPhone and iPad, use the [App Store](https://aka.ms/powerappsios).
+
+  - For Android devices, use [Google Play](https://aka.ms/powerappsandroid).
+
+- Ensure that your organization has deployed and configured the Employee Return to the Workplace app, as described in [Deploy the solution](deploy.md).
+
+## Getting started with the app
+
+Open the app from your device and sign in with your company's Azure Active Directory account. You can view all apps shared with you by your organization after you sign in. More information: [Power Apps mobile device sign in](https://docs.microsoft.com/powerapps/user/run-app-client#open-power-apps-and-sign-in)
+
+When you successfully sign in and open the **Return to the Workplace** app from your mobile device, you can get a day pass, look up facility status, or answer the employee sentiment question.
+
+> [!div class="mx-imgBorder"]
+> ![Welcome screen](media/employee-welcome2.png "Welcome screen")
+
+## See the reopen status of a facility
+
+You can find all available facilities and see the reopen status for them. Select **Look Up Status** to look for facilities and view details such as whether the facility is open and what phase of reopening it's in.
+
+When you select a facility from the facility list, the current status of the facility and associated details are displayed. Select **<** to return to the home screen.
+
+> [!div class="mx-imgBorder"]
+> ![List of facilities](media/employee-facility-list2.png "List of facilities")
+
+> [!div class="mx-imgBorder"]
+> ![Facility details](media/employee-facility-details2.png "Facility details")
+
+## Check in to a facility
+
+After you complete the steps to select a particular facility that's open to employees returning to work, you can complete a health survey that determines whether you're eligible to check in to that facility. 
+
+If you're eligible, you'll be given a pass to your selected building for that day. 
+
+**To check in to a facility**
+
+1. Select **GET DAY PASS**.
+
+2. Select an available facility from the facility list.
+
+3. Select **Start Health Survey** to complete the check-in process.
+
+   > [!div class="mx-imgBorder"]
+   > ![Start survey](media/employee-start-survey2.png "Start survey")
+
+4. Accept the terms and agreements.
+
+    > [!div class="mx-imgBorder"]
+    > ![Terms and agreements](media/employee-termandagreement.png "Terms and agreements")
+
+5. Review the **Symptom Check** statements. Select **I Agree**  if you agree with the statements, and **I Disagree** if you don't.
+
+   > [!div class="mx-imgBorder"]
+   > ![Symptom check](media/employee-agreement.png "Symptom check")
+
+### Employee pass
+
+If your responses to the symptom check statements show that you're healthy, you'll receive a pass to enter the selected facility. The pass expires in 24 hours. 
+
+> [!div class="mx-imgBorder"]
+> ![Employee pass](media/employee-pass.png "Employee pass")
+
+If your responses show you aren't healthy, you won't receive a pass and you'll be given contact information for the company health and safety department to use if you need.
+
+> [!div class="mx-imgBorder"]
+> ![Not feeling well](media/employee-pass-negative.png "Not feeling well")
+
+## Share sentiment
+
+You can say how you're feeling about returning to the workplace. On the home page, select one of the options to answer the question **Do you feel safe returning to work?**
+
+> [!div class="mx-imgBorder"]
+> ![Share sentiment](media/employee-share-sentiment2.png "Share sentiment")
+
+ This option will reset itself after you reopen the app.
+
+> [!div class="mx-imgBorder"]
+> ![Share sentiment](media/employee-share-sentiment2-2.png "Share sentiment")
+
+## Feedback about the solution
+
+To provide feedback about the Return to the Workplace solution, visit <https://aka.ms/rtw-community>.