Merge branch 'main' into 2684293

Author: ProfessorKendrick

powerapps-docs/developer/component-framework/reference/dataset/addColumn.md

@@ -27,10 +27,10 @@ Model-driven apps
 
 ## Parameters
 
-| Parameter Name | Type     | Required | Description          |
-| -------------- | -------- | -------- | -------------------- |
-| name           | `string` | Yes      | Name of the column.  |
-| columnAlias    | `string` | No       | Alias of the column. |
+| Parameter Name | Type     | Required | Description                                                                                                                          |
+| -------------- | -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| name           | `string` | Yes      | Name of the column. For linked entities concatenate linking entity alias and the column name, for example: `contact_alias.firstname`. |
+| columnAlias    | `string` | No       | Alias of the column.                                                                                                                 |
 
 ## Return value
 

powerapps-docs/developer/data-platform/application-insights-ilogger.md

@@ -168,15 +168,13 @@ namespace ILoggerExample
 
                         HttpResponseMessage response = client
                             .GetAsync(webAddress)
-                            .ConfigureAwait(false)
                             .GetAwaiter()
                             .GetResult(); //Make sure it is synchronous
 
                         response.EnsureSuccessStatusCode();
 
                         string responseText = response.Content
                             .ReadAsStringAsync()
-                            .ConfigureAwait(false)
                             .GetAwaiter()
                             .GetResult(); //Make sure it is synchronous
 

powerapps-docs/developer/data-platform/best-practices/business-logic/set-timeout-for-external-calls-from-plug-ins.md

@@ -56,10 +56,10 @@ using (HttpClient client = new HttpClient())
   client.DefaultRequestHeaders.ConnectionClose = true; //Set KeepAlive to false
   
 
-  HttpResponseMessage response =  client.GetAsync(webAddress).ConfigureAwait(false).GetAwaiter().GetResult(); //Make sure it is synchronous
+  HttpResponseMessage response =  client.GetAsync(webAddress).GetAwaiter().GetResult(); //Make sure it is synchronous
   response.EnsureSuccessStatusCode();
 
-  string responseText = response.Content.ReadAsStringAsync().ConfigureAwait(false).GetAwaiter().GetResult(); //Make sure it is synchronous
+  string responseText = response.Content.ReadAsStringAsync().GetAwaiter().GetResult(); //Make sure it is synchronous
   tracingService.Trace(responseText);
   //Log success in the Plugin Trace Log:
   tracingService.Trace("HttpClientPlugin completed successfully.");

powerapps-docs/developer/data-platform/create-custom-api-maker-portal.md

@@ -2,7 +2,7 @@
 title: "Create a Custom API in Power Apps (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Create a Custom API definition with the maker portal" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 03/21/2022
+ms.date: 04/19/2022
 ms.reviewer: "jdaly"
 ms.topic: "article"
 author: "divka78" # GitHub ID
@@ -71,7 +71,7 @@ For example, if your Custom API Unique name is `sample_CustomAPIExample`, it wil
 
 ## Observe the result in the service document
 
-If you haven't set the `IsPrivate` property for your Custom API, you can now retrieve the service definition from the [CSDL $metadata document](webapi/web-api-types-operations.md#csdl-metadata-document) using a GET request, even from your browser. If the url for your environment is `https://yourorg.crm.dynamics.com`, you can type this URL in your browser address field to retrieve the $metadata: `https://yourorg.crm.dynamics.com/api/data/v9.1/$metadata`.
+If you haven't set the `IsPrivate` property for your Custom API, you can now retrieve the service definition from the [CSDL $metadata document](webapi/web-api-service-documents.md#csdl-metadata-document) using a `GET` request, even from your browser. If the url for your environment is `https://yourorg.crm.dynamics.com`, you can type this URL in your browser address field to retrieve the $metadata: `https://yourorg.crm.dynamics.com/api/data/v9.1/$metadata`.
 
 Search the result to find the name of the Custom API. For example, the API defined using the steps above looks like this:
 

powerapps-docs/developer/data-platform/create-custom-api-prt.md

@@ -1,7 +1,7 @@
 ---
 title: "Create a Custom API using the plug-in registration tool (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Create a Custom API using the plug-in registration tool" # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 03/13/2022
+ms.date: 04/19/2022
 ms.reviewer: "jdaly"
 ms.topic: "article"
 author: "marcelbf" # GitHub ID
@@ -120,7 +120,7 @@ In the list of **Request parameters** or **Response properties**, select this co
 
 ## Next steps
 
-If you haven't set the `IsPrivate` property for your Custom API, after you have created your Custom API you can retrieve the service definition from the [CSDL $metadata document](webapi/web-api-types-operations.md#csdl-metadata-document) using a GET request, even from your browser. If the url for your environment is `https://yourorg.crm.dynamics.com`, you can type this URL in your browser address field to retrieve the $metadata: `https://yourorg.crm.dynamics.com/api/data/v9.1/$metadata`.
+If you haven't set the `IsPrivate` property for your Custom API, after you have created your Custom API you can retrieve the service definition from the [CSDL $metadata document](webapi/web-api-service-documents.md#csdl-metadata-document) using a `GET` request, even from your browser. If the url for your environment is `https://yourorg.crm.dynamics.com`, you can type this URL in your browser address field to retrieve the $metadata: `https://yourorg.crm.dynamics.com/api/data/v9.1/$metadata`.
 
 Search the result to find the name of the Custom API and you will find the Action or Function created together with any related ComplexType to represent the return value. For example:
 

powerapps-docs/developer/data-platform/custom-api.md

@@ -2,7 +2,7 @@
 title: "Create and use Custom APIs (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Custom API is a new code-first way to define custom messages for the Microsoft Dataverse" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 03/21/2022
+ms.date: 04/19/2022
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "divka78" # GitHub ID
@@ -137,7 +137,7 @@ You may want to keep a Custom API private until you are sure that you will not n
 You can leave **Is Private** set to false in your development environment so you can see the output in the $metadata service document or generate classes for your own use. However, before you ship the Custom API in your managed solution, you should set **Is Private** to true.
 
 More information: 
-- [CSDL $metadata document](webapi/web-api-types-operations.md#csdl-metadata-document)
+- [CSDL $metadata document](webapi/web-api-service-documents.md#csdl-metadata-document)
 - [Generate early-bound classes for the Organization service](org-service/generate-early-bound-classes.md)
 - [Private Messages](org-service/use-messages.md#private-messages)
 
@@ -453,7 +453,7 @@ A: You cannot. Although these records have the common **Status** and **Status Re
 
 ### Q: How can I use my private messages if they are not included in the Web API $metadata service document?
 
-A: Your private messages will work regardless of whether they are advertised in the Web API [CSDL $metadata document](webapi/web-api-types-operations.md#csdl-metadata-document) or not. While you develop your solution, you can leave the `IsPrivate` value set to `false`. This way you can refer to the `$metadata` listing and use code generation tools that depend on this data. However, you should set the `CustomAPI.IsPrivate` value to `true` before you ship your solution for others to use. If you later decide that you wish to support other applications to use the message, you can change the `CustomAPI.IsPrivate` value to `false`.
+A: Your private messages will work regardless of whether they are advertised in the Web API [CSDL $metadata document](webapi/web-api-service-documents.md#csdl-metadata-document) or not. While you develop your solution, you can leave the `IsPrivate` value set to `false`. This way you can refer to the `$metadata` listing and use code generation tools that depend on this data. However, you should set the `CustomAPI.IsPrivate` value to `true` before you ship your solution for others to use. If you later decide that you wish to support other applications to use the message, you can change the `CustomAPI.IsPrivate` value to `false`.
 
 More information:
 

powerapps-docs/developer/data-platform/entities.md

@@ -1,12 +1,11 @@
 ---
 title: Work with Dataverse tables using code | Microsoft Docs
 description: Learn about programmatically working with tables in Microsoft Dataverse.
-author: "mayadumesh" # GitHub ID
-manager: kvivek
-
-ms.date: 03/28/2021
+author: mayadumesh # GitHub ID
+manager: sunilg
+ms.date: 04/19/2022
 ms.subservice: dataverse-developer
-ms.author: jdaly
+ms.author: mayadu
 search.audienceType: 
   - developer
 search.app: 
@@ -72,7 +71,7 @@ The table definition includes the following information:
 
 ## Private tables
 
-Dataverse contains some tables that are not intended for third-party developers to use. These tables are added by Microsoft to enable feature functionality. Private tables are indicated by the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.IsPrivate> property. These tables are not included in the Web API [CSDL $metadata document](webapi/web-api-types-operations.md#csdl-metadata-document). However, you will find them when querying entity metadata.
+Dataverse contains some tables that are not intended for third-party developers to use. These tables are added by Microsoft to enable feature functionality. Private tables are indicated by the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.IsPrivate> property. These tables are not included in the Web API [CSDL $metadata document](webapi/web-api-service-documents.md#csdl-metadata-document). However, you will find them when querying entity metadata.
 
 > [!CAUTION]
 > You should not use private tables in your solutions. By marking a table as private, Microsoft is explicitly indicating that we do not support other apps to use the table. Microsoft may remove the table or introduce breaking changes at any time. Use of these tables by anyone other than Microsoft is not supported.

powerapps-docs/developer/data-platform/reference/about-entity-reference.md

@@ -3,7 +3,7 @@ title: "Dataverse table/entity reference | Microsoft Docs"
 description: "Use this reference to understand the available operations that can be performed for specific tables, the default columns/attributes of each table/entity and the relationships between tables in Microsoft Dataverse"
 author: phecke
 ms.topic: reference
-ms.date: 04/03/2022
+ms.date: 04/19/2022
 ms.author: pehecke
 ms.reviewer: jdaly
 manager: kvivek
@@ -65,7 +65,7 @@ For each one-to-many relationship, the following properties are included:
 |`ReferencingAttribute`|The logical name of the column in the related table that contains a reference to primary key of the primary table.|
 |`IsHierarchical`|Whether the relationship represents a self-referential hierarchical relationship|
 |`IsCustomizable`|Whether the properties of the relationship can be changed.|
-|`ReferencedEntityNavigationPropertyName`|The name of the Web API collection-valued navigation property for this relationship.<br />More information:[Navigation properties](../webapi/web-api-types-operations.md#navigation-properties)|
+|`ReferencedEntityNavigationPropertyName`|The name of the Web API collection-valued navigation property for this relationship.<br />More information: [Web API Navigation Properties](../webapi/web-api-navigation-properties.md)|
 |`AssociatedMenuConfiguration`|Data used by model-driven apps to control whether and how the related entity data can be accessed in the UI from the primary entity.|
 |`CascadeConfiguration`|Data that describes which operations performed on the parent entity will cascade down to related entities.<br />More information: [Cascade configuration](../entity-relationship-metadata.md#cascade-configuration)|
 
@@ -80,7 +80,7 @@ For each many-to-many relationship the following properties are included:
 |`IntersectEntityName`|The logical name of the intersect table that supports this many-to-many relationship|
 |`Entity1LogicalName`|The logical name for the first table in the relationship.|
 |`Entity1IntersectAttribute`|The logical name of the intersect table column that includes a reference to the primary key of the first table.|
-|`Entity1NavigationPropertyName`|The name of the Web API collection-valued navigation property for this relationship.<br />More information: [Navigation properties](../webapi/web-api-types-operations.md#navigation-properties)|
+|`Entity1NavigationPropertyName`|The name of the Web API collection-valued navigation property for this relationship.<br />More information: [Web API Navigation Properties](../webapi/web-api-navigation-properties.md)|
 |`Entity1AssociatedMenuConfiguration`|Data used by model-driven apps to control whether and how the first table data can be accessed in the UI from the second table.|
 |`Entity2LogicalName`|The logical name for the second table in the relationship.|
 |`Entity2IntersectAttribute`|The logical name of the intersect table column that includes a reference to the primary key of the second table.|

powerapps-docs/developer/data-platform/troubleshoot-plug-in.md

@@ -38,7 +38,7 @@ This error simply means that the worker process running your plug-in code crashe
 
 As mentioned in [Handle exceptions in plug-ins](handle-exceptions.md), when you write a plug-in you should try to anticipate which operations may fail and wrap them in a try-catch block. When any errors occur, you should use the <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> to gracefully terminate the operation with an error meaningful to the user.
 
-A common scenario for this is when using a the [HttpClient.SendAsync Method](/dotnet/api/system.net.http.httpclient.sendasync?view=netframework-4.6.2) or [HttpClient.GetAsync Method](/dotnet/api/system.net.http.httpclient.getasync?view=netframework-4.6.2) which are asynchronous operations that returns a [Task](/dotnet/api/system.threading.tasks.task-1?view=netframework-4.6.2). To make this work in a plug-in where code needs to be synchronous, people may use the [Task&lt;TResult&gt;.Result Property](/dotnet/api/system.threading.tasks.task-1.result?view=netframework-4.6.2). When an error occurs, this returns an [AggregateException](/dotnet/api/system.aggregateexception?view=netframework-4.6.2) which consolidates multiple failures into a single exception which can be difficult to handle. A better design is to use [Task&lt;TResult&gt;.ConfigureAwait(false)](/dotnet/api/system.threading.tasks.task-1.configureawait?view=netframework-4.6.2).[GetAwaiter()](/dotnet/api/system.aggregateexception?view=netframework-4.6.2).[GetResult()](/dotnet/api/system.runtime.compilerservices.taskawaiter-1.getresult?view=netframework-4.6.2) because it propagates the results as the specific error that caused the failure.
+A common scenario for this is when using a the [HttpClient.SendAsync Method](/dotnet/api/system.net.http.httpclient.sendasync?view=netframework-4.6.2) or [HttpClient.GetAsync Method](/dotnet/api/system.net.http.httpclient.getasync?view=netframework-4.6.2) which are asynchronous operations that returns a [Task](/dotnet/api/system.threading.tasks.task-1?view=netframework-4.6.2). To make this work in a plug-in where code needs to be synchronous, people may use the [Task&lt;TResult&gt;.Result Property](/dotnet/api/system.threading.tasks.task-1.result?view=netframework-4.6.2). When an error occurs, this returns an [AggregateException](/dotnet/api/system.aggregateexception?view=netframework-4.6.2) which consolidates multiple failures into a single exception which can be difficult to handle. A better design is to use [Task&lt;TResult&gt;.GetAwaiter()](/dotnet/api/system.threading.tasks.task-1.getawaiter?view=netframework-4.6.2).[GetResult()](/dotnet/api/system.runtime.compilerservices.taskawaiter-1.getresult?view=netframework-4.6.2) because it propagates the results as the specific error that caused the failure.
 
 The following example shows the correct way to manage the exception and an outbound call using [HttpClient.GetAsync Method](/dotnet/api/system.net.http.httpclient.getasync?view=netframework-4.6.2). This plug-in will attempt to get the response text for a Url set in the unsecure config for a step registered for it.
 
@@ -93,12 +93,12 @@ namespace ErrorRepro
                     client.Timeout = TimeSpan.FromMilliseconds(15000); //15 seconds
                     client.DefaultRequestHeaders.ConnectionClose = true; //Set KeepAlive to false
 
-                    HttpResponseMessage response = client.GetAsync(webAddress).ConfigureAwait(false).GetAwaiter().GetResult(); //Make sure it is synchronous
+                    HttpResponseMessage response = client.GetAsync(webAddress).GetAwaiter().GetResult(); //Make sure it is synchronous
                     response.EnsureSuccessStatusCode();
 
                     tracingService.Trace($"ErrorRepro.AsyncError.GetWebResponse succeeded.");
 
-                    string responseContent = response.Content.ReadAsStringAsync().ConfigureAwait(false).GetAwaiter().GetResult(); //Make sure it is synchronous
+                    string responseContent = response.Content.ReadAsStringAsync().GetAwaiter().GetResult(); //Make sure it is synchronous
 
                     tracingService.Trace($"ErrorRepro.AsyncError.GetWebResponse responseContent parsed successfully.");
 

powerapps-docs/developer/data-platform/use-change-tracking-synchronize-data-external-systems.md

@@ -1,7 +1,7 @@
 ---
 title: "Use change tracking to synchronize data with external systems (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "The change tracking feature provides a way to keep the data synchronized in an efficient manner by detecting what data has changed since the data was initially extracted or last synchronized" # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 03/22/2022
+ms.date: 04/19/2022
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "Peakerbl" # GitHub ID
@@ -19,8 +19,6 @@ contributors:
 ---
 # Use change tracking to synchronize data with external systems
 
-
-
 The change tracking feature in Microsoft Dataverse provides a way to keep the data synchronized in an efficient manner by detecting what data has changed since the data was initially extracted or last synchronized. Previously, without this new feature, it was difficult to build a reliable and efficient mechanism to determine what records had changed in Dataverse. This article discusses how to retrieve changes for a table.  
 
 ## Enable change tracking for a table  
@@ -30,7 +28,7 @@ The change tracking feature in Microsoft Dataverse provides a way to keep the da
  ```http 
  GET [Organization URI]/api/data/v9.0/$metadata?annotations=true
  ```
- Read more about metadata annotations on [Metadata annotations](webapi/web-api-types-operations.md#bkmk_metannot).
+ Read more about metadata annotations on [Metadata annotations](webapi/web-api-service-documents.md#metadata-annotations).
 
  For more information about using the customization user interface (UI), see [Enable change tracking to control data synchronization](/power-platform/admin/enable-change-tracking-control-data-synchronization).