Merge branch 'master' into portals-powerbi

Author: tapanm-MSFT

powerapps-docs/developer/common-data-service/authenticate-dot-net-framework.md

@@ -2,7 +2,7 @@
 title: "Authentication with .NET Framework applications (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "How .NET Framework applications can authenticate with Common Data Service" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 01/25/2019
+ms.date: 05/11/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -48,6 +48,7 @@ More information: [Build Windows client applications using the XRM tools](xrm-to
 Use .NET Framework version 4.6.2 or higher when you create client applications. Only applications using Transport Level Security (TLS) 1.2 or better security can connect. TLS 1.2 is not the default protocol used by .NET Framework 4.5.2, but it is in .NET Framework 4.6.2.
 
 > [!NOTE]
+> The SDK APIs available in [Microsoft.CrmSdk.XrmTooling.CoreAssembly](https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.CoreAssembly/) and other "CrmSdk" NuGet packages do not support .NET Core code development. Revised packages (containing refactored APIs) that do support .NET Core development can be found here: [Microsoft.Powerplatform.Cds.Client](https://www.nuget.org/packages/Microsoft.Powerplatform.Cds.Client/) and [Microsoft.Dynamics.Sdk.Messages](https://www.nuget.org/packages/Microsoft.Dynamics.Sdk.Messages/).<p/>
 > **Known Issue with Visual Studio 2015**
 > 
 > When you are running your project/solution in VS 2015 in debug mode, you may not be able to connect. This happens regardless of whether you are using a Target Framework of 4.6.2 or higher. This can occur because the Visual Studio hosting process is compiled against .NET 4.5 which means by default it does not support TLS 1.2. You can disable the Visual Studio hosting process as a work around. 

powerapps-docs/developer/common-data-service/best-practices/work-with-metadata/retrieve-published-metadata.md

@@ -60,7 +60,7 @@ public RetrieveAllEntitiesAttributesResponse GetAllEntitiesImplicit(IOrganizatio
 }
 ```
 
-### Explictly controlling the behavior
+### Explicitly controlling the behavior
 
 Explicitly setting the `RetrieveAsIfPublished` property to retrieve only published customizations
 

powerapps-docs/developer/common-data-service/cds-sql-query.md

@@ -25,13 +25,16 @@ A SQL data connection is available on the Common Data Service endpoint. The SQL
 > [!IMPORTANT]
 > - This is a preview feature, and isn't available in all regions.
 > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
+> - Instructions to enable the feature can be found here: [View entity data in Power BI Desktop](/powerapps/maker/common-data-service/view-entity-data-power-bi).
 
 ## Applications support
 
 You can use the **Analyze in Power BI** option (**Data** > **Entities** > **Analyze in Power BI**) in Power Apps (https://make.powerapps.com) to use the SQL connection feature to analyze data in Power BI Desktop. More information: [View entity data in Power BI Desktop](/powerapps/maker/common-data-service/view-entity-data-power-bi)
 
 > [!NOTE]
-> If you don't have the **Analyze in Power BI** option in your Power Apps environment, you don't yet have access to the SQL connection feature.
+> To verify if your target environment has the Common Data Service SQL connection feature enabled, do the following:
+> 1. Sign into Power Apps, on the left navigation pane expand **Data**, and then select **Entities**.
+> 2. On the command bar, you should see a button **Analyze in Power BI**. If you do not see this button, your environment does not yet have the feature.
 
 You can also use [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) (SSMS) version 18.4 or later with the Common Data Service endpoint SQL connection. Examples of using SSMS with the SQL data connection are provided below.
 

powerapps-docs/developer/common-data-service/online-management-api/sample-quick-start.md

@@ -13,9 +13,9 @@ search.audienceType:
 search.app: 
   - PowerApps
 ---
-# Quick Start Sample: Retrieve Common Data Service environements using Online Management API 
+# Quick Start Sample: Retrieve Common Data Service environments using Online Management API 
 
-The C# sample demonstrates how to authenticate to the Online Management API and then retrieve all Common Data Service environements from your Office 365 tenant.
+The C# sample demonstrates how to authenticate to the Online Management API and then retrieve all Common Data Service environments from your Office 365 tenant.
 
 The sample uses the authentication [helper code](sample-authentication-helper.md) to easily authenticate to Online Management API using the OAuth 2.0 protocol and pass in the access token in header of your request.
 
@@ -30,7 +30,7 @@ The sample performs the following tasks:
     b. Uses an HttpClient instance to connect to Online Management API service.
 
     c. Specifies the API service base address and the max period of execution time.
-1. Uses the **RetrieveInstancesAsync** method to execute a http request to retrieve all Customer Enagement instances in your Office 365 tenant, and then displays the reponse.
+1. Uses the **RetrieveInstancesAsync** method to execute a http request to retrieve all Customer Engagement instances in your Office 365 tenant, and then displays the response.
 
 ## Run this sample
 Before you can run this sample, make sure that you have:

powerapps-docs/developer/common-data-service/org-service/metadata-attributemetadata.md

@@ -502,7 +502,7 @@ Console.WriteLine("Created {0} with the value of {1}.",
 
  This sample code shows how to change the order of options in a local option set. The following sample retrieves a custom <xref:Microsoft.Xrm.Sdk.Metadata.PicklistAttributeMetadata> attribute and changes the order of the original options using the [OrderBy](https://msdn.microsoft.com/library/system.linq.enumerable.orderby.aspx)**LINQ** function to sort items in ascending order by the label text. Then it uses <xref:Microsoft.Xrm.Sdk.Messages.OrderOptionRequest> to set the new order of the options for the attribute.  
 
- Use the [OrderByDecending](https://msdn.microsoft.com/library/system.linq.enumerable.orderbydescending.aspx) linq function to order the items in descending order.  
+ Use the [OrderByDescending](https://msdn.microsoft.com/library/system.linq.enumerable.orderbydescending.aspx) linq function to order the items in descending order.  
 
 ```csharp
 // Use the RetrieveAttributeRequest message to retrieve  

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

@@ -141,8 +141,8 @@ The classes in the <xref:Microsoft.Xrm.Sdk.Metadata.Query> namespace and the <xr
      EntityFilter.Conditions.Add(new MetadataConditionExpression("IsIntersect", MetadataConditionOperator.Equals, false));
      EntityFilter.Conditions.Add(new MetadataConditionExpression("OwnershipType", MetadataConditionOperator.Equals, OwnershipTypes.UserOwned));
      EntityFilter.Conditions.Add(new MetadataConditionExpression("SchemaName", MetadataConditionOperator.NotIn, excludedEntities));
-     MetadataConditionExpression isVisibileInMobileTrue = new MetadataConditionExpression("IsVisibleInMobile", MetadataConditionOperator.Equals, true);
-     EntityFilter.Conditions.Add(isVisibileInMobileTrue);
+     MetadataConditionExpression isVisibleInMobileTrue = new MetadataConditionExpression("IsVisibleInMobile", MetadataConditionOperator.Equals, true);
+     EntityFilter.Conditions.Add(isVisibleInMobileTrue);
 ```
 
 ### Specify the properties you want

powerapps-docs/developer/common-data-service/use-multi-tenant-server-server-authentication.md

@@ -62,12 +62,12 @@ In this scenario any Common Data Service tenant can potentially use your multi-t
  You will create a multi-tenant web application or service which uses Azure AD as the authentication provider.  
 
  Exactly how you do this will not be the focus of this topic. There are a number of ways you can approach this and make choices that fit your requirements or preferences. See the following links for more information and samples:  
+
+- [Build a multi-tenant SaaS web application using Azure AD & OpenID Connect](https://github.com/Azure-Samples/active-directory-dotnet-webapp-multitenant-openidconnect)
 
-- [Build a multi-tenant SaaS web application using Azure AD & OpenID Connect](https://azure.microsoft.com/documentation/samples/active-directory-dotnet-webapp-multitenant-openidconnect/)  
-  
-- [Build a multi-tenant SaaS web application that calls a web API using Azure AD](https://azure.microsoft.com/documentation/samples/active-directory-webapp-webapi-multitenant-openidconnect-aspnetcore/)  
+- [An ASP.NET Core Web app signing-in users in any org with the Microsoft identity platform](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/1-WebApp-OIDC/1-2-AnyOrg)  
 
-  Azure AD requires the following values to register your application:  
+Azure AD requires the following values to register your application:  
 
 |Value|Description|  
 |-----------|-----------------|  

powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md

@@ -14,7 +14,7 @@ ms.topic: "article"
 
 # Add code components to a field or entity in model-driven apps
 
-Code components let you transform fields that traditionally contain text into visualizations. Similarly, you can use code components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. code components can appear as visualizations on forms, dashboards, views, and homepage grids. 
+Code components let you transform fields that traditionally contain text into visualizations. Similarly, you can use code components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. Code components can appear as visualizations on forms, dashboards, views, and homepage grids. 
 
 
    > [!div class="mx-imgBorder"] 
@@ -93,4 +93,4 @@ To add a code component like data-set component or simple table component to a g
 
 [Implementing components in TypeScript](implementing-controls-using-typescript.md)<br/>
 [Power Apps component framework API reference](reference/index.md)<br/>
-[Power Apps component framework overview](overview.md)
+[Power Apps component framework overview](overview.md)

powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md

@@ -19,9 +19,9 @@ This article demonstrates how to create and deploy code components using Power A
 
 ## Create a new component
 
-To begin, open **Developer Command Prompt for VS 2017** after installing Power Apps CLI.
+To begin, open **Developer Command Prompt for VS 2017 or higher** after installing Power Apps CLI.
 
-1. In the Developer Command Prompt for VS 2017, create a new folder on your local machine, for example, *C:\Users\your name\Documents\My_code_Component* using the command `mkdir <Specify the folder name>`.
+1. In the Developer Command Prompt, create a new folder on your local machine, for example, *C:\Users\your name\Documents\My_code_Component* using the command `mkdir <Specify the folder name>`.
 2. Go to the newly created folder using the command `cd <specify your new folder path>`.
 3. Create a new component project by passing some basic parameters using the command:
 

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

@@ -29,7 +29,7 @@ The following steps are required to build a linear slider code component:
 
 To create a new project:
 
-1. Open a **Developer Command Prompt for VS 2017** window. Create a new folder for the project using the following command: 
+1. Open a **Developer Command Prompt for VS 2017 or higher** window. Create a new folder for the project using the following command: 
     ```CLI
      mkdir LinearComponent
     ```
@@ -374,7 +374,7 @@ Follow these steps to create and import a [solution](https://docs.microsoft.com/
     > [!NOTE]
     > Make sure that **NuGet targets & Build Tasks** is checked. To enable it:
     > - Open **Visual Studio Installer**.
-    > - For Visual Studio 2017, select **Modify**.
+    > - For Visual Studio 2017 or higher, select **Modify**.
     > - Select **Individual Components**.
     > - Under **Code Tools**, check **NuGet targets & Build Tasks**.