Merge branch 'live' into patch-1

Author: tapanm-MSFT

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/developer/common-data-service/virtual-entities/sample-generic-ve-plugin.md

@@ -27,6 +27,9 @@ search.app:
 
 This sample shows a minimal implementation for a generic Common Data Service virtual entity data provider plug-in, **DropboxRetrieveMultiplePlugin**, for the [Dropbox](https://www.dropbox.com/) file-sharing service. It uses the "bare metal" approach, translating the <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> through the creation of the custom visitor class, **DropBoxExpressionVisitor**. It returns a collection of the files that satisfy the search criteria as an <xref:Microsoft.Xrm.Sdk.EntityCollection>. 
 
+> [!NOTE]
+> This sample requires the use of ILMERGE to combine the plug-in and Dropbox assemblies prior to registering the assembly with Common Data Service. Use of ILMERGE is not officially supported. A future update to this sample will remove the need to use ILMERGE. 
+
 ## Getting started
 
 In order to build this sample, you must first install the [Dropbox.Api](https://www.nuget.org/packages/Dropbox.Api/) and [Microsoft.CrmSdk.Data](https://www.nuget.org/packages/Microsoft.CrmSdk.Data/) NuGet packages in your solution.  You'll also need a DropBox account and pass a real access token when creating an instance of the **DropboxClient**.
@@ -119,4 +122,4 @@ public class DropboxRetrieveMultiplePlugin : IPlugin
 
 [Get started with virtual entities](get-started-ve.md)<br />
 [API considerations of virtual entities](api-considerations-ve.md)<br />
-[Custom virtual entity data providers](custom-ve-data-providers.md)
+[Custom virtual entity data providers](custom-ve-data-providers.md)

powerapps-docs/developer/common-data-service/walkthrough-register-app-azure-active-directory.md

@@ -66,8 +66,10 @@ App registration can also be done by an application developer or individual user
 7. Search for and choose **Common Data Service** under the **APIs my organization uses** tab.
 
     ![Select API](media/app-registration-select-api-page.png "Select API")    
-
-8. Click on **Delegated permissions** and check the options and click on **Add permissions**. 
+    > [!TIP]
+    > If you are presented with more than one **Common Data Service** item in the search list, choose any one of them. In the next step the service name and URL will be shown. At that point you can go back to the API search and choose a different Common Data Service list item if needed.
+    
+8.  Click on **Delegated permissions** and check the options and click on **Add permissions**. 
 
     ![Delegate Permissions](media/app-registration-delegate-permissions-page.png "Delegate Permission")
     > [!NOTE]

powerapps-docs/developer/common-data-service/webapi/enhanced-quick-start.md

@@ -68,7 +68,7 @@ Edit the `<configuration>` element to add a the `connectionStrings` node as show
   <connectionStrings>
     <!--Online using Office 365-->
     <add name="Connect"
-         connectionString="Url=https://yourorg.api.crm.dynamics.com;[email protected];Password=y0urp455w0rd; />
+         connectionString="Url=https://yourorg.api.crm.dynamics.com;[email protected];Password=mypassword;" />
   </connectionStrings>
 </configuration>
 ```