Merge branch 'master' into LanceDelano

Author: lancedMicrosoft

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

@@ -33,6 +33,8 @@
       href: column-comparison.md
     - name: FetchXML search item limit
       href: quick-find-limit.md
+    - name: Improve FetchXML request performance
+      href: fetchxml-performance.md
   - name: "Use SQL to query data (Preview)"
     href: cds-sql-query.md
   - name: Saved Queries

powerapps-docs/developer/common-data-service/cds-sql-query.md

@@ -2,7 +2,7 @@
 title: "Use SQL to query data (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to query Common Data Service entity data using SQL." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 05/26/2020
+ms.date: 09/25/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -20,8 +20,13 @@ search.app:
 
 [!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
+> [!WARNING]
+> A problem has been identified with the Tabular Data Stream (TDS) endpoint. This feature is globally disabled, and we are working urgently to address the issue. This topic will be updated when the issue is resolved or when we have more information to share.
+
 A SQL data connection is available on the Common Data Service endpoint. The SQL connection provides read-only access to the entity data of the target Common Data Service environment. This allows you to write and execute SQL queries against the entity data table. Table columns provide the attribute data of the entity. No custom views of the data have been provided.
 
+
+
 > [!IMPORTANT]
 > - This is a preview feature, and isn't available in all regions.
 > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]

powerapps-docs/developer/common-data-service/fetchxml-performance.md

@@ -0,0 +1,117 @@
+---
+title: Improve FetchXML request performance | Microsoft Docs
+description: Learn how developers can improve FetchXML request performance when using Common Data Service.
+author: NHelgren
+manager: annbe
+ms.service: powerapps
+ms.topic: article
+ms.date: 09/28/2020
+ms.author: nhelgren
+ms.reviewer: "pehecke"
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+
+# Improve FetchXML request performance
+
+An option available in FetchXML requests called *LateMaterialize* allows you to break up such
+requests into smaller more usable segments which can improve the performance of long running FetchXML requests.
+
+> [!NOTE]
+> Performance improvements depend on the data distribution for each
+> participating entity and linked entity. Late materialization may not always
+> provide a performance benefit. It is best used if you are experiencing
+> performance issues with your existing fetch request.
+
+Executing a traditional fetch for a given number of the top entity records will pull all
+the columns in the select list that meet the filter criteria. Let’s say you are
+pulling the top 500 records on an entity that has 100 columns and 100K rows
+that meet the filter criteria, this request can cause issues in two ways:
+
+- The 99.5K rows will pull all columns, even though you only need to populate
+  the select list for 500 rows when returning to the client.
+
+- Query Optimizer can generate an arbitrary order when retrieving the child
+  columns, resulting in an undesired data order.
+
+Using `LateMaterialize` allows you to create a fetch that will:
+
+- First pull only the primary ID of the top number of records specified.
+
+- Select only the columns of data needed based on the primary IDs that were
+  retrieved. For example, where only 5 columns are needed for display in the form.
+
+By pulling only the needed data after the primary IDs are collected, the
+retrieval is much faster as data that is not needed for the current operation is
+excluded.
+
+This is most beneficial when:
+
+- The entity you are querying has one or more links to other entities for column data.
+
+- There are many columns in the entity.
+
+- The entity contains logical attributes.
+
+## Syntax
+
+```xml
+<fetch version="1.0" output-format="xml-platform" latematerialize="true"
+ mapping="logical" distinct="true">
+
+  <entity name="[entity]">​
+    <attribute name="[attribute]" />
+​
+    <link-entity name="[entity]" from="[linked entity]" to="[linked entityid]"
+                 link-type="outer" alias="[alias]">​
+      <attribute name="[name of linked entity column]" />​
+    </link-entity>
+​
+    <filter type=[filter type]>​
+      <condition attribute="[column]" operator="[operator]" value="[value]"/> ​
+    </filter>​
+  </entity>
+​
+</fetch>
+```
+
+## Sample
+
+```XML
+<fetch version="1.0" output-format="xml-platform" latematerialize="true"
+       mapping="logical" distinct="true">
+
+  <entity name="account">​
+    <attribute name="accountnumber" />​
+    <attribute name="createdby" />​
+    <attribute name="ownerid" />​
+
+    <link-entity name="account" from="accountid" to="parentaccountid"
+                 link-type="outer" alias="oaccount">​
+      <attribute name="createdby" />
+​
+      <link-entity name="account" from="accountid" to="accountid" link-type="outer"
+                 alias="oaccount1">​
+        <attribute name="createdby" />​
+        <attribute name="accountid" />​
+        <attribute name="name" />​
+      </link-entity>​
+    </link-entity>​
+
+    <link-entity name="account" from="accountid" to="accountid" link-type="outer"
+                 alias="oaccount2"/>
+​
+    <filter type='and'>​
+      <condition attribute="statecode" operator="eq" value="2"/> ​
+    </filter>​
+  </entity>​
+
+</fetch>
+```
+
+### See Also
+
+[Use FetchXML to construct a query](use-fetchxml-construct-query.md)

powerapps-docs/maker/TOC.yml

@@ -1449,6 +1449,8 @@
           href: ./portals/configure/gather-feedback-poll.md
         - name: Create and manage publishing states
           href: ./portals/configure/publishing-states.md
+        - name: Create custom Portal Management app
+          href: ./portals/configure/create-custom-portal-management-app.md
     - name:  Advanced portal customization
       items:
         - name: Work with Liquid templates
@@ -1830,6 +1832,8 @@
           href: ../teams/relationships-table.md
         - name: Work with table columns
           href: ../teams/table-columns.md
+        - name: Project Oakdale FAQs
+          href: ../teams/data-platform-faqs.md
     - name: Manage your apps
       href: ../teams/manage-your-apps.md
     - name: Publish and share your app

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

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: 
-ms.date: 07/02/2020
+ms.date: 09/22/2020
 ms.author: kvivek
 search.audienceType: 
   - maker
@@ -28,7 +28,7 @@ This article lists some common issues that you might encounter while using Power
    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.**
 
 1. **Problems downloading attachments in SharePoint custom forms** (May 22, 2020)
-   When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, change to use the default SharePoint form or use another browser. The team is actively working to fix this issue. **Fix has been deployed in the weeek of 6/8/2020**
+   When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, change to use the default SharePoint form or use another browser. The team is actively working to fix this issue. **Fix has been deployed in the week of 6/8/2020**
 
 1. **Problems downloading attachments in embedded Power Apps** (May 22, 2020)
   When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, use another browser. The team is actively working to fix this issue.
@@ -207,3 +207,7 @@ This article lists some common issues that you might encounter while using Power
 1. **Card gallery is deprecated**.
 
      Existing apps that use this feature will continue to run for the time being, but you can't add a card gallery. Please replace card galleries with the new **[Edit form](controls/control-form-detail.md)** and **[Display form](controls/control-form-detail.md)** controls.
+     
+ 1.   **Power Apps per app plans does not support Power Apps for Windows app**
+ 
+        Power Apps for Windows app is not supported if you're on the [Power Apps per app plans](https://docs.microsoft.com/power-platform/admin/about-powerapps-perapp). 

powerapps-docs/maker/canvas-apps/controls/control-microphone.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: reference
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 06/12/2020
+ms.date: 09/28/2020
 ms.author: chmoncay
 search.audienceType: 
   - maker
@@ -40,6 +40,14 @@ Captured media is referenced by a text string URI. For more information, read th
 > [!NOTE]
 > The microphone control is supported only on Microsoft Edge based on Chromium, Chrome, and Firefox browsers; and Android and iOS devices. All other browsers and platforms will show a warning that some features of the app won't work.
 
+## Considerations for Teams Mobile
+
+The following conditions apply when using the Microphone control in apps created using Power Apps on Teams Mobile:
+
+1. The audio format for microphone recordings in Teams will always be *AAC* with a file extension of .MP4.
+1. Teams has its own recording experience. Hence, the microphone control inside apps created using Power Apps will be disabled during the recording period.
+1. Microphone recordings are limited to a maximum duration of 10 minutes.
+
 ## Key properties
 
 **Audio** – The audio clip captured when the user records with the device's microphone. 

powerapps-docs/maker/canvas-apps/functions/function-patch.md

@@ -7,14 +7,15 @@ ms.service: powerapps
 ms.topic: reference
 ms.custom: canvas
 ms.reviewer: nabuthuk
-ms.date: 03/16/2020
+ms.date: 09/25/2020
 ms.author: gregli
 search.audienceType: 
   - maker
 search.app: 
   - PowerApps
 ---
 # Patch function in Power Apps
+
 Modifies or creates one or more [records](../working-with-tables.md#records) in a [data source](../working-with-data-sources.md), or merges records outside of a data source.
 
 Use the **Patch** function to modify records in complex situations. Such as, when you do updates that require no user interaction or use forms that span multiple screens.
@@ -95,16 +96,16 @@ Specify two or more records that you want to merge. Records are processed in the
 #### Modify or create a record (in a data source)
 In these examples, you'll modify or create a record in a data source, named **IceCream**, that contains the data in this [table](../working-with-tables.md) and automatically generates the values in the **ID** [column](../working-with-tables.md#columns):
 
-![](media/function-patch/icecream.png)
+![Example icecream](media/function-patch/icecream.png "Example icecream")
 
 | Formula | Description | Result |
 | --- | --- | --- |
-| **Patch(&nbsp;IceCream,<br>First( Filter( IceCream, Flavor = "Chocolate" ) ), {&nbsp;Quantity:&nbsp;400&nbsp;} )** |Modifies a record in the **IceCream** data source:<ul><li> The **ID** column of the record to modify contains the value of **1**. (The **Chocolate** record has that ID.)</li><li>The value in the **Quantity** column changes to **400**. |{&nbsp;ID:&nbsp;1, Flavor:&nbsp;"Chocolate", Quantity:&nbsp;400 }<br><br>The **Chocolate** entry in the **IceCream** data source has been modified. |
+| **Patch(&nbsp;IceCream,<br>Lookup( IceCream, Flavor = "Chocolate" ), {&nbsp;Quantity:&nbsp;400&nbsp;} )** |Modifies a record in the **IceCream** data source:<ul><li> The **ID** column of the record to modify contains the value of **1**. (The **Chocolate** record has that ID.)</li><li>The value in the **Quantity** column changes to **400**. |{&nbsp;ID:&nbsp;1, Flavor:&nbsp;"Chocolate", Quantity:&nbsp;400 }<br><br>The **Chocolate** entry in the **IceCream** data source has been modified. |
 | **Patch( IceCream, Defaults(&nbsp;IceCream ), {&nbsp;Flavor:&nbsp;"Strawberry"&nbsp;}&nbsp;)** |Creates a record in the **IceCream** data source:<ul><li>The **ID** column contains the value **3**, which the data source generates automatically.</li><li>The **Quantity** column contains **0**, which is the default value for that column in the **IceCream** data source, as the **[Defaults](function-defaults.md)** function specifies.<li>The **Flavor** column contains the value of **Strawberry**.</li> |{ ID:&nbsp;3, Flavor:&nbsp;"Strawberry", Quantity:&nbsp;0&nbsp;}<br><br>The **Strawberry** entry in the **IceCream** data source has been created. |
 
 After the previous formulas have been evaluated, the data source ends with these values:
 
-![](media/function-patch/icecream-after.png)
+![Example icecream after](media/function-patch/icecream-after.png "Example icecream after")
 
 #### Merge records (outside of a data source)
 
@@ -113,11 +114,12 @@ After the previous formulas have been evaluated, the data source ends with these
 | **Patch(&nbsp;{&nbsp;Name:&nbsp;"James",&nbsp;Score:&nbsp;90&nbsp;}, {&nbsp;Name:&nbsp;"Jim",&nbsp;Passed:&nbsp;true&nbsp;} )** |Merges two records outside of a data source:<br><ul><li>The values in the **Name** column of each record don't match. The result contains the value (**Jim**) in the record that's closer to the end of the argument list instead of the value (**James**) in the record that's closer to the start.</li><li>The first record contains a column (**Score**) that doesn't exist in the second record. The result contains that column with its value (**90**).</li><li>The second record contains a column (**Passed**) that doesn't exist in the first record. The result contains that column with its value (**true**). |{&nbsp;Name:&nbsp;"Jim", Score:&nbsp;90, Passed:&nbsp;true&nbsp;} |
 
 ### Use of **As** or **ThisRecord**
-Avoid an ambiguous evaluation context by using the **As** or **ThisRecord** keyword. 
 
-In the example below, consider the first Lookup in the If statement. (OrderID = A[@OrderID]) is expected to compare the OrderId in the Lookup scope with the OrderId of collection A in the ForAll scope. In this case, you likely want A[@OrderId] to be resolved as a local parameter. But it is ambiguous.
+Using the **As** or **ThisRecord** keyword in the formula avoids ambiguous evaluation context. 
+
+In the example below, consider the first lookup in the `If` statement. `(OrderID = A[@OrderID])` is expected to compare the `OrderId` in the lookup scope with the `OrderId` of collection `A` in the `ForAll` scope. In this case, you likely want `A[@OrderId]` to be resolved as a local parameter. But it is ambiguous.
 
-Power Apps currently interprets both the LHS side OrderId and RHS side A[@OrderId] as a field in the Lookup scope. Therefore, Lookup will always find the first row in [dbo].[Orders1] because the condition is always true (i.e., any row's OrderId is equal to itself.)
+Power Apps currently interprets both the left-hand side `OrderId` and right-hand side `A[@OrderId]` as a field in the lookup scope. Therefore, lookup will always find the first row in `[dbo].[Orders1]` because the condition is always true (that is, any row's `OrderId` is equal to itself.)
 
 ```powerapps-dot
 ClearCollect(
@@ -158,11 +160,11 @@ ForAll(
 
 #### Using **As** or **ThisRecord**
 
-Whenever possible use the **As** operator or the **ThisRecord** to disambiguate the LHS. **As** is recommended for the above scenario.
+Whenever possible use the **As** operator or the **ThisRecord** to disambiguate the left-hand side. **As** is recommended for the above scenario.
 
-When your formula uses multiple scopes with ForAll, Filter, Lookup on the same data source or table, it is possible that the scope parameters may collide with a same named field elsewhere.  Therefore, it is also recommended to use the **As** operator or **ThisRecord** to resolve the field name and avoid ambiguity.
+When your formula uses multiple scopes with `ForAll`, `Filter`, and `Lookup` on the same data source or table, it is possible that the scope parameters may collide with a same field elsewhere.  Therefore, it is recommended to use the **As** operator or **ThisRecord** to resolve the field name and avoid ambiguity.
 
-For example, we can use the **As** operator to disambiguate in the example below. 
+For example, you can use the **As** operator to disambiguate in the example below. 
 
 ```powerapps-dot
 ClearCollect(
@@ -201,7 +203,7 @@ ForAll(
 )
 ```
 
-Alternatively, we can use **ThisRecord** for the same purpose.
+Alternatively, you can use **ThisRecord** for the same purpose.
 
 ```powerapps-dot
 ClearCollect(
@@ -239,7 +241,8 @@ ForAll(
     )
 )
 ```
-For detailed usage of the **As** operator and **ThisRecord**. For details, please see the **[Operators](operators.md)** article.
+
+To learn more about the usage of **As** operator and **ThisRecord** see **[Operators](operators.md)** article.
 
 
 

powerapps-docs/maker/canvas-apps/functions/function-update-updateif.md

@@ -43,7 +43,7 @@ Both **Update** and **UpdateIf** return the modified data source as a [table](..
 * *DataSource* – Required. The data source that contains the record that you want to replace.
 * *OldRecord* – Required. The record to replace.
 * *NewRecord* – Required. The replacement record. This isn't a change record. The entire record is replaced, and missing properties will contain *blank*.
-* **All** – Optional. In a collection, the same record may appear more than once. Specify the **All** argument to remove all copies of the record.
+* *All* – Optional. In a collection, the same record may appear more than once. Specify the **All** argument to update all copies of the record.
 
 **UpdateIf**( *DataSource*, *Condition1*, *ChangeRecord1* [, *Condition2*, *ChangeRecord2*, ... ] )