Merge branch 'master' into pehecke-error-codes-update

Author: phecke

powerapps-docs/developer/common-data-service/best-practices/business-logic/avoid-batch-requests-plugin.md

@@ -31,7 +31,7 @@ search.app:
 
 ## Symptoms
 
-Due to their long-running nature, using <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.ExecuteTransactionRequest> message request classes within the context of a plug-in or workflow activity expose sandbox-isolated plug-in types to the two-minute (12000ms) channel timeout exception and can degrade the user experience for synchronous registrations.
+Due to their long-running nature, using <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.ExecuteTransactionRequest> message request classes within the context of a plug-in or workflow activity expose sandbox-isolated plug-in types to the two-minute (120000ms) channel timeout exception and can degrade the user experience for synchronous registrations.
 
 
 <a name='guidance'></a>

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

@@ -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/entity-metadata.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/multi-select-picklist.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/org-service/metadata-retrieve-detect-changes.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/org-service/use-filterexpression-class.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.|  

powerapps-docs/developer/common-data-service/org-service/use-messages.md

@@ -84,7 +84,7 @@ More information:
 
 You can pass optional parameters in messages using the <xref:Microsoft.Xrm.Sdk.OrganizationRequest.Parameters> property that is exposed for all the *Request message classes in the SDK assemblies. There are two optional parameters you can pass with messages
 
-|`Parameter`|Description|Messages|  
+|Parameter|Description|Messages|  
 |-----------------|-----------------|--------------|  
 |`SolutionUniqueName`|A `String` that specifies the unique name of the solution to which the operation applies. More information: [Dependency tracking for solution components](../dependency-tracking-solution-components.md).|<xref:Microsoft.Crm.Sdk.Messages.AddPrivilegesRoleRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.DeleteRequest> <br /> <xref:Microsoft.Crm.Sdk.Messages.MakeAvailableToOrganizationTemplateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|  
 |`SuppressDuplicateDetection`|A `Boolean` used to disable duplicate detection on a create or update operation. More information: [Use SuppressDuplicateDetection parameter to throw errors when you create or update record](detect-duplicate-data.md#use-suppressduplicatedetection-parameter-to-throw-errors-when-you-create-or-update-record) .|<xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|  

powerapps-docs/developer/common-data-service/store-appsource-package-azure-storage.md

@@ -35,40 +35,39 @@ To upload your package to Azure Blob storage:
 2. Sign in to Azure Management portal at [https://portal.azure.com](https://portal.azure.com).
 3. Create a new Storage account by clicking  > **Storage** > **Storage account - blob, file, table, queue**.
 
-   ![](media/appsource-storageaccount-pic1.png)
+   Create a Storage account](media/appsource-storageaccount-pic1.png)
 
 4. On the **Create storage account** page, specify **Name**, **Resource group**, and **Location** for your storage account. Leave the rest of the fields with the default options. Click **Create**. 
 
-   ![](media/appsource-storageaccount-pic2.png)
- 
+   ![Specifying account values](media/appsource-storageaccount-pic2.png)
 
 5. After your storage account is created, navigate to the newly created resource group, and create a new Blob container. Under **Blob Service**, select **Containers**, and then **+ Container**.
 
-   ![](media/appsource-storageaccount-pic3.png)
+   ![Create a new Blob container](media/appsource-storageaccount-pic3.png)
 
 6. Specify a name for your container, and select the **Public access level** as **Blob**. Click **OK**.
 
-   ![](media/appsource-storageaccount-pic4.png)
+   ![Set access level of the Blob](media/appsource-storageaccount-pic4.png)
 
 7. Start Azure Storage Explorer on your computer, and connect to your Azure Storage account by signing in using the same account with which you created your Azure Storage account.
 
 8. In Azure Storage Explorer, select the newly created container, and then select **Upload** > **Upload Files** to upload the app source package that you created in [Step 4: Create an AppSource package for your app](create-package-app-appsource.md). 
 
-   ![](media/appsource-storageaccount-pic5.png)
+   ![Upload the app source package](media/appsource-storageaccount-pic5.png)
 
 9. Browse to the AppSource package file on your computer, and select to upload it.
 
 10. Right-click on the uploaded AppSource package file, and select **Get Shared Access Signature**.
 
-    ![](media/appsource-storageaccount-pic6.png)
+    ![Selecting Shared Access Signature](media/appsource-storageaccount-pic6.png)
 
 11. On the **Shared Access Signature** page, modify the **Expiry time** value to make the Shared Access Signature (SAS) active for a month from the **Start time**. Click **Create**.
 
-    ![](media/appsource-storageaccount-pic7.png)
+    ![Set an expiration time](media/appsource-storageaccount-pic7.png)
 
 12. The next page displays information about the generated SAS information. Copy the **URL** value and save it for later. You will need to specify this URL while creating an offer in the Cloud Partner Portal.
 
-    ![](media/appsource-storageaccount-pic8.png)
+    ![Copying the SAS URL](media/appsource-storageaccount-pic8.png)
 
 
 > [!div class="nextstepaction"]

powerapps-docs/developer/common-data-service/use-webhooks.md

@@ -339,7 +339,7 @@ Webhooks are relatively simple. The service will send the request and evaluate t
 
 The timeout is 60 seconds. Generally, if no response is returned before the timeout period or if the response `StatusCode` value is not within the `2xx` range to indicate success it will fail. The exception is when the error returned is in the following table:
 
-|`StatusCode`|Description|
+|StatusCode|Description|
 |-|-|
 |`502`|Bad Gateway|
 |`503`|Service Unavailable|

powerapps-docs/developer/common-data-service/webapi/use-postman-perform-operations.md

@@ -143,9 +143,9 @@ More information: [Update and delete entities using the Web API](update-delete-e
 
 ## Use a function
 
-Use a `GET` request with the functions listed in [Web API Function Reference](https://docs.microsoft.com/dynamics365/customer-engagement/web-api/functions?view=dynamics-ce-odata-9) to perform reusable operations with the Web API. The example that follows shows how to send a Web API request that uses the <xref href="Microsoft.Dynamics.CRM.RetrieveDuplicates?text=RetrieveDuplicates function" /> to detect and retrieve duplicates of a specified record.
+Use a `GET` request with the functions listed in [Web API Function Reference](https://docs.microsoft.com/dynamics365/customer-engagement/web-api/functions?view=dynamics-ce-odata-9) to perform reusable operations with the Web API. The example that follows shows how to send a Web API request that uses the <xref:Microsoft.Dynamics.CRM.RetrieveDuplicates?text=RetrieveDuplicates function /> to detect and retrieve duplicates of a specified record.
 
-|||
+|HTTP method|URL|
 |----|----|
 |`GET`|`{{webapiurl}}RetrieveDuplicates(BusinessEntity=@p1,MatchingEntityName=@p2,PagingInfo=@p3)?@p1={'@odata.type':'Microsoft.Dynamics.CRM.account','accountid':'`*&lt;accountid&gt;*`'}&@p2='account'&@p3={'PageNumber':1,'Count':50}`|