Merge branch 'master' into teams-ga

Author: KumarVivek

.acrolinx-config.edn

@@ -1,12 +1,5 @@
 {:allowed-branchname-matches ["^master$"]
  :allowed-filename-matches ["powerapps-docs"]
- :targets
- {
-     :scores
-     {
-         :qualityscore 80
-     }
- }
  :guidance-profile "dc59e3ef-24fd-46d7-9156-0491aaae6bef" ;; Profile ID for "BAG-specific" 
  :acrolinx-check-settings
  {

powerapps-docs/developer/common-data-service/best-practices/business-logic/optimize-assembly-development.md

@@ -14,7 +14,7 @@ ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 1/15/2019
-ms.author: phecke
+ms.author: pehecke
 search.audienceType: 
   - developer
 search.app: 

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: 09/25/2020
+ms.date: 11/09/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -22,9 +22,8 @@ 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 presently globally disabled as we work to address a security issue. A fix for the issue has been developed. Deployment of the fix and feature re-enablement to all public regions is planned for the first week of November 2020. A safe deployment practice is being followed so the feature may be available in your region earlier. Thank you for your patience on this matter.
-
+> [!IMPORTANT]
+> This feature has been re-enabled in the majority of regions. Please resume testing, and provide feedback. We thank you for your patience and feedback.
 
 
 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.

powerapps-docs/developer/common-data-service/customize-entity-attribute-mappings.md

@@ -73,7 +73,7 @@ For more information see [Create a new entity record from another entity](webapi
  You can edit attribute mappings between entities for entity relationships that support mapping. 
 
  In addition to creating each attribute map manually, you can use the 
- `AutoMapEntity` message(<xref href="Microsoft.Dynamics.CRM.AutoMapEntity?text=AutoMapEntity Action" /> or <xref:Microsoft.Crm.Sdk.Messages.AutoMapEntityRequest> class) to generate a new set of attribute mappings. This message performs the action found under the **Generate Mappings** menu option in the **More Actions** menu on the toolbar (see [Automatically generate field mappings](../../maker/common-data-service/map-entity-fields.md#automatically-generate-field-mappings)). This message maps all the attributes between the two related entities where the attribute names and types are identical. This message is provided as a productivity enhancement so that you do not have to manually add all attribute mappings. Instead, you can generate a set of likely mappings and minimize the amount of manual work to add or remove individual mappings to meet your requirements. 
+ `AutoMapEntity` message(<xref href="Microsoft.Dynamics.CRM.AutoMapEntity?text=AutoMapEntity Action" /> or <xref:Microsoft.Crm.Sdk.Messages.AutoMapEntityRequest> class) to generate a new set of attribute mappings. This message performs the action found under the **Generate Mappings** menu option in the **More Actions** menu on the toolbar (see [Automatically generate column mappings](../../maker/common-data-service/map-entity-fields.md#automatically-generate-column-mappings)). This message maps all the attributes between the two related entities where the attribute names and types are identical. This message is provided as a productivity enhancement so that you do not have to manually add all attribute mappings. Instead, you can generate a set of likely mappings and minimize the amount of manual work to add or remove individual mappings to meet your requirements. 
 
 > [!NOTE]
 > Automatically generating mappings in this manner will remove any previously defined attribute mappings and may include mappings that you do not want.  
@@ -100,4 +100,4 @@ For more information see [Create a new entity record from another entity](webapi
 
 ### See also
 
- [Map entity fields](../../maker/common-data-service/map-entity-fields.md)
+ [Map entity fields](../../maker/common-data-service/map-entity-fields.md)

powerapps-docs/developer/common-data-service/media/isv-failure-details-drill-through.png

@@ -37,7 +37,8 @@ For more information about actions, see [Use actions](/powerapps/maker/common-da
 
 ## Returns
 
-On success, returns Web API result along with any action output.
+On success, returns an object with the Web API result along with any action output.
+On failure, returns an object with error details.
 
 ### Related topics
 [Use actions](/powerapps/maker/common-data-service/actions)

powerapps-docs/developer/common-data-service/media/isv-install-error-details.png

@@ -523,6 +523,126 @@ Xrm.WebApi.online.execute(deleteRequest).then(
 );
 ```
 
+### Associate a record
+The following code sample demonstrates how to perform an Associate operation on collection-valued navigation properties (Many-To-One and Many-To-Many relationships). For single-valued navigation properties (One-To-Many relationships a.k.a Lookup fields), you can perform an Update operation as shown above or use [Xrm.WebApi.updateRecord](../updateRecord.md).
+
+```JavaScript
+var Sdk = window.Sdk || {};
+
+/*
+ * Request to execute an Associate operation.
+ */
+Sdk.AssociateRequest = function(target, relatedEntities, relationship) {
+    this.target = target;
+    this.relatedEntities = relatedEntities;
+    this.relationship = relationship;
+};
+
+// NOTE: The getMetadata property should be attached to the function prototype instead of the
+// function object itself.
+Sdk.AssociateRequest.prototype.getMetadata = function() {
+    return {
+        boundParameter: null,
+        parameterTypes: {},
+        operationType: 2, // Associate and Disassociate fall under the CRUD umbrella
+        operationName: "Associate"
+    }
+};
+
+// Construct the target EntityReference object
+var target = {
+    entityType: "account",
+    id: "0b4abc7d-7619-eb11-8dff-000d3ac5c7f9"
+};
+
+// Construct the related EntityReferences that the Target will be associated with.
+var relatedEntities = [
+    {
+        entityType: "contact",
+        id: "180a9aad-7619-eb11-8dff-000d3ac5c7f9"
+    },
+    {
+        entityType: "contact",
+        id: "753c58b4-7619-eb11-8dff-000d3ac5c7f9"
+    }
+];
+
+// The name of the existing relationship to associate on.
+var relationship = "new_account_contact";
+
+var manyToManyAssociateRequest = new Sdk.AssociateRequest(target, relatedEntities, relationship)
+
+Xrm.WebApi.online.execute(manyToManyAssociateRequest).then(
+    function(result) {
+        if (result.ok) {
+            console.log("Status: %s %s", result.status, result.statusText);
+            // perform other operations as required;
+        }
+    }, 
+    function(error) {
+        console.log(error.message);
+        // handle error conditions
+    }
+);
+```
+
+### Disassociate a record
+The following code sample demonstrates how to perform a Disassociate operation on collection-valued navigation properties (Many-To-One and Many-To-Many relationships). For single-valued navigation properties (One-To-Many relationships a.k.a Lookup fields), you can perform an Update operation as shown above or use [Xrm.WebApi.updateRecord](../updateRecord.md).
+
+> [!NOTE]
+> Unlike the Associate operation which allows associating the target entity record with multiple related entity records in a single operation, the Disassociate operation is limited to only disassociating one entity record from the target entity record per operation.
+
+```JavaScript
+var Sdk = window.Sdk || {};
+
+/*
+ * Request to execute a Disassociate operation.
+ */
+Sdk.DisassociateRequest = function(target, relatedEntityId, relationship) {
+    this.target = target;
+    this.relatedEntityId = relatedEntityId;
+    this.relationship = relationship;
+};
+
+// NOTE: The getMetadata property should be attached to the function prototype instead of the
+// function object itself.
+Sdk.DisassociateRequest.prototype.getMetadata = function() {
+    return {
+        boundParameter: null,
+        parameterTypes: {},
+        operationType: 2, // Associate and Disassociate fall under the CRUD umbrella
+        operationName: "Disassociate"
+    }
+};
+
+// Construct the target EntityReference object
+var target = {
+    entityType: "account",
+    id: "0b4abc7d-7619-eb11-8dff-000d3ac5c7f9"
+};
+
+// The GUID of the related entity record to disassociate.
+var relatedEntityId = "180a9aad-7619-eb11-8dff-000d3ac5c7f9";
+
+// The name of the existing relationship to disassociate from.
+var relationship = "new_account_contact";
+
+var manyToManyDisassociateRequest = new Sdk.DisassociateRequest(target, relatedEntityId, relationship)
+
+Xrm.WebApi.online.execute(manyToManyDisassociateRequest).then(
+    function(result) {
+        if (result.ok) {
+            console.log("Status: %s %s", result.status, result.statusText);
+            // perform other operations as required;
+        }
+    }, 
+    function(error) {
+        console.log(error.message);
+        // handle error conditions
+    }
+);
+```
+
 ### Related topics