Merge remote-tracking branch 'origin/master' into matp-export-data-lake

Author: Mattp123

.openpublishing.redirection.json

@@ -39,7 +39,7 @@ There are three levels where auditing can be configured: organization, entity, a
 
  The following table lists the non-customizable entities that cannot be audited. This table was obtained by testing for a `CanModifyAuditSettings` attribute value of `false` on each entity’s metadata.  
 
-||  
+|Non-customizable entities|  
 |-|  
 |ActivityPointer|  
 |Annotation|  

powerapps-docs/developer/common-data-service/configure-entities-attributes-auditing.md

@@ -44,7 +44,7 @@ A package lets you bundle and deploy multiple files related to your app at once.
 
     ```xml
     <?xml version="1.0" encoding="utf-8"?>
-    <Types xmlns="https://schemas.openxmlformats.org/package/2006/content-types">
+    <Types xmlns="http://schemas.openxmlformats.org/package/2006/content-types">
       <Default Extension="xml" ContentType="application/octet-stream" />
       <Default Extension="xaml" ContentType="application/octet-stream" />
       <Default Extension="dll" ContentType="application/octet-stream" />

powerapps-docs/developer/common-data-service/create-package-app-appsource.md

@@ -2,7 +2,7 @@
 title: "Work with alternate keys (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "The topic explains about how to create alternate keys for an entity. Alternate keys can be created programmatically or by using the customization tools" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 06/24/2020
+ms.date: 08/01/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -23,7 +23,7 @@ All Common Data Service records have unique identifiers defined as GUIDs. These
 
 ## Create alternate keys  
 
-You can create alternate keys programmatically or by using the customizations tools. For more information about using the customization tools, see [Define alternate keys to reference CRM records](https://technet.microsoft.com/library/29e53691-0b18-4fde-a1d0-7490aa227898.aspx).  
+You can create alternate keys programmatically or by using the customizations tools. For more information about using the customization tools, see [Define alternate keys using Power Apps portal](../../maker/common-data-service/define-alternate-keys-portal.md).
 
 To define alternate keys programmatically, you first have to create an object of type <xref:Microsoft.Xrm.Sdk.Metadata.EntityKeyMetadata> (or use <xref href="Microsoft.Dynamics.CRM.EntityKeyMetadata?text=EntityKeyMetadata EntityType" /> if working with Web API). This class contains the key attributes. Once the key attributes are set, you can use `CreateEntityKey` to create the keys for an entity. This message takes the entity name and `EntityKeyMetadata` values as input to create the key.  
 
@@ -54,7 +54,7 @@ You should be aware of the following constraints when creating alternate keys:
 
 - **Unicode characters in key value**
 
-  If the data within a field that is used in an alternate key will contain one of the following characters `/`,`<`,`>`,`*`,`%`,`&`,`:`,`\\` then update or upsert (PATCH) actions will not work.  If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
+  If the data within a field that is used in an alternate key will contain one of the following characters `/`,`<`,`>`,`*`,`%`,`&`,`:`,`\\`,`?` then retrieve (`GET`), update or upsert (`PATCH`) actions will not work.  If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
 
 <a name="BKMK_crud"></a>   
 

powerapps-docs/developer/common-data-service/define-alternate-keys-entity.md

@@ -177,7 +177,7 @@ Some entities will have different sets of options.
 **Example**: `PhoneCall` entity `StateCode` and `StatusCode` options
 
 
-|`StateCode`|`StatusCode`|
+|StateCode|StatusCode|
 |---------|---------|
 |0 : Open|1: Open|
 |1 : Completed|2: Made <br />4: Received|

powerapps-docs/developer/common-data-service/entity-metadata.md

@@ -89,7 +89,7 @@ The following examples shows the use of `ContainValues` and `not-contain-values`
 
 ### Contact entity values
 
-|`fullname`| `sample_outdooractivities` |
+|'fullname' attribute| 'sample_outdooractivities' attribute |
 |--------|-------------------|
 |Wayne Yarborough|1,9|
 |Monte Orton|2|

powerapps-docs/developer/common-data-service/includes/data-service-errors.md

@@ -83,7 +83,7 @@ The classes in the <xref:Microsoft.Xrm.Sdk.Metadata.Query> namespace and the <xr
 
  The following table lists <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata> properties that cannot be used in a <xref:Microsoft.Xrm.Sdk.Metadata.Query.MetadataFilterExpression>:  
 
-|||||  
+|Properties|Properties (cont'd)|Properties (cont'd)|Properties (cont'd)|  
 |-|-|-|-|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.Attributes>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.Description>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.DisplayCollectionName>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.DisplayName>|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ManyToManyRelationships>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ManyToOneRelationships>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.OneToManyRelationships>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.Privileges>|  
@@ -249,7 +249,7 @@ EntityProperties.PropertyNames.AddRange(new string[] { "Attributes" });
 
  The following table lists <xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata> properties that cannot be used in a <xref:Microsoft.Xrm.Sdk.Metadata.Query.MetadataFilterExpression>  
 
-|||  
+|Properties|Properties (cont'd)|  
 |-|-|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata.Description>|<xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata.DisplayName>|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.EnumAttributeMetadata.OptionSet>|<xref:Microsoft.Xrm.Sdk.Metadata.LookupAttributeMetadata.Targets>|  
@@ -283,7 +283,7 @@ AttributeProperties.PropertyNames.Add("AttributeType");
 
  The following table lists Relationship metadata properties that cannot be used in a MetadataFilterExpression:  
 
-||  
+|Properties|  
 |-|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata.AssociatedMenuConfiguration>|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata.CascadeConfiguration>|  

powerapps-docs/developer/common-data-service/multi-select-picklist.md

@@ -2,7 +2,7 @@
 title: "Use the ConditionExpression class (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Read how you can use the ConditionExpression class to compare an attribute to a value or set of values by using an operator, such as "equal to" or "greater than"" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 08/03/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -105,20 +105,28 @@ public ConditionExpression
 )
 ```
 
-In the SDK, two APIs are introduced to support column comparison. The
-first identifies the original attribute, the second allows
-for the inclusion of the attribute you want to compare it against.
+By passing in `true` as the value for the `compareColumns` parameter, the `value` is treated as the
+name of the second attribute to compare the values in `attributeName` to. Pass in `false` to treat it
+as a literal value instead.
 
-If `compareColumns` is passed in as `true`, it will compare the two attributes
-and return all records that match.
+For example:
 
-If a `false` value is passed, it will return all records for one attribute and
-return values that match the provided value.
+```csharp
+new ConditionExpression("firstname", ConditionOperator.Equal, true, "lastname");
+```
+
+This code creates a condition to return only records where the first and last names are the same, while
+
+```csharp
+new ConditionExpression("firstname", ConditionOperator.Equal, false, "John");
+```
+
+creates a condition to return only records where the first name is John.
 
 More information: [Use column comparison in queries](../column-comparison.md)
 
 ### See also  
  [Building Queries](build-queries-with-queryexpression.md)   
  [Build Queries with QueryExpression](build-queries-with-queryexpression.md)   
  [Use the FilterExpression Class](use-filterexpression-class.md)   
- <xref:Microsoft.Xrm.Sdk.Query.ConditionExpression>
+ <xref:Microsoft.Xrm.Sdk.Query.ConditionExpression>

powerapps-docs/developer/common-data-service/org-service/metadata-retrieve-detect-changes.md

@@ -21,9 +21,8 @@ In Common Data Service, you can use the <xref:Microsoft.Xrm.Sdk.Query.FilterExpr
 
  The following table lists the properties for the <xref:Microsoft.Xrm.Sdk.Query.FilterExpression> class.  
 
-|||  
-|-|-|  
-|Property|Description|  
+|Property|Description|
+|-|-|
 |<xref:Microsoft.Xrm.Sdk.Query.FilterExpression.Conditions>|Gets or sets condition expressions that include attributes, condition operators, and attribute values.|  
 |<xref:Microsoft.Xrm.Sdk.Query.FilterExpression.FilterOperator>|Gets or sets logical `AND/OR` filter operators. This is set by using the <xref:Microsoft.Xrm.Sdk.Query.LogicalOperator> enumeration.|  
 |<xref:Microsoft.Xrm.Sdk.Query.FilterExpression.Filters>|Gets or sets a hierarchy of condition and logical filter expressions that filter the results of the query.|