Merge branch 'master' into portal-simplified-auth-1784365

Author: tapanm-MSFT

.openpublishing.redirection.json

@@ -1635,6 +1635,11 @@
       "source_path": "powerapps-docs/maker/common-data-service/view-download-developer-resources.md",
       "redirect_url": "https://docs.microsoft.com/powerapps/developer/common-data-service/view-download-developer-resources",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "powerapps-docs/developer/common-data-service/use-web-services.md",
+      "redirect_url": "https://docs.microsoft.com/powerapps/developer/common-data-service/work-with-data-cds",
+      "redirect_document_id": true
     }
   ]
 }

powerapps-docs/developer/common-data-service/api-limits.md

@@ -2,7 +2,7 @@
 title: "Impersonate another user (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Use impersonation to execute business logic on behalf of another Common Data Service user to provide a desired feature or service using the appropriate role and object-based security of that impersonated user." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 04/07/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -46,7 +46,7 @@ More information: [Build web applications using Server-to-Server (S2S) authentic
 
 ## Impersonate another user using the Web API
 
-To impersonate a user, add a request header named `MSCRMCallerID` with a GUID value equal to the impersonated user’s `systemuserid` before sending the request to the web service. 
+To impersonate a user, add a request header named `CallerObjectId` with a GUID value equal to the impersonated user's Azure Active Directory (AAD) object id before sending the request to the web service. The user's AAD object id is included in the [SystemUser.AzureActiveDirectoryObjectId](reference/entities/systemuser.md#BKMK_AzureActiveDirectoryObjectId).
 
 More information: [Impersonate another user using the Web API](webapi/impersonate-another-user-web-api.md).
 
@@ -70,3 +70,4 @@ More information: [Impersonate a user](impersonate-a-user.md).
 [Build web applications using Server-to-Server (S2S) authentication](build-web-applications-server-server-s2s-authentication.md)<br />
 [Impersonate another user using the Web API](webapi/impersonate-another-user-web-api.md)<br />
 [Write a plug-in](write-plug-in.md)
+ 

powerapps-docs/developer/common-data-service/impersonate-another-user.md

@@ -1,6 +1,6 @@
 ---
 title: Introduction to the AppSource checker | Microsoft Docs
-description: Learn how to use app source checker.
+description: Learn how to use AppSource checker
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -25,39 +25,41 @@ search.app:
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
-AppSource checker allows an ISV to check the certification criteria of their app prior to [AppSource](https://appsource.microsoft.com/) submission. The checker will let you know if your solution file has errors that need to be corrected or if AppSource certification criteria have not been met. 
+You can use the AppSource checker to verify whether your app has met certification criteria before you submit it to [AppSource](https://appsource.microsoft.com/). The checker lets you know whether your solution file has errors that need to be corrected and verifies whether AppSource certification criteria have been met. 
 
-In ISV Studio, an ISV can either upload a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s) and be notified of any issues that need to be remediated. To do that:
+In ISV Studio, you can upload either a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s). You'll be notified whether any issues need to be remediated.
 
-1. In ISV Studio, select **AppSource checker** tab in the left and then select **Validate your app**.
+**To run AppSource checker**
+
+1. In ISV Studio, select **AppSource checker** in the leftmost pane, and then select **Validate your app**.
 
     > [!div class="mx-imgBorder"]
-    > ![AppSource checker](media/appsource-checker.png)
+    > ![AppSource checker](media/appsource-checker.png "AppSource checker")
 
-2. Click on **Browse** to upload a solution file from your local machine and select **Run Check** to validate.
+2. Select **Browse** to upload a solution file from your local machine, and then select **Run Check**.
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-browse-solution-files.png)
+   > ![Run check command](media/appsource-browse-solution-files.png "Run check command")
  
    > [!NOTE]
-   > If a user has previously uploaded a solution for validation then you will see a history of submissions instead of the screenshot above.
+   > If you've previously uploaded a solution for validation, you'll see a history of submissions instead of the screenshot above.
 
-3. Once the solution checker completes validating, a summary of results will be displayed along with the number of issues present (if any). Double-click on the solution file to see the issues in detail.
+3. After the validation check is complete, a summary of results is displayed with the number of issues found (if any). Double-click to select the solution file to see the issues in detail.
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-results-page.png)
+   > ![Summary of AppSource checker results](media/appsource-results-page.png "Summary of AppSource checker results")
 
-4. If the submission has no errors, you will see the following message:
+4. If the submission has no errors, you'll see the following message:
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-no-error-page.png)
+   > ![AppSource checker success message](media/appsource-no-error-page.png "AppSource checker success message")
    
-5. An ISV can download the validation report for their app and include it with their AppSource submission. 
+Now you can download the validation report for your app and include it with your AppSource submission. 
 
-## See Also
+### See also
 
 [Home page](isv-app-management-homepage.md)<br/>
 [App page](isv-app-management-apppage.md)<br/>
 [Tenant page](isv-app-management-tenantpage.md)<br/>
-[Connector Certification](isv-app-management-certification.md)
+[Connector certification](isv-app-management-certification.md)
 

powerapps-docs/developer/common-data-service/isv-app-management-appsource-checker.md

@@ -1,6 +1,6 @@
 ---
 title: Connector certification from ISV Studio | Microsoft Docs
-description: Learn how to submit a custom connector for certification using ISV Studio.
+description: Learn how to submit a custom connector for certification by using ISV Studio.
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -21,40 +21,42 @@ search.app:
   - D365CE
 ---
 
-# Connector Certification
+# Connector certification
 
-If you own a service, API, or built a custom connector that you want to connect to Power Apps, Power Automate, Azure Logic Apps, or Power Query, you need to submit your connector to Microsoft for certification. 
+If you own a service or API—or you've built a custom connector that you want to connect to Power Apps, Power Automate, Azure Logic Apps, or Power Query—you need to submit your connector to Microsoft for certification. 
 
-Connector Certification is now in ISV Studio allowing the users to manage and track their connector certification submission. More information: [Get your connector certified](https://docs.microsoft.com/connectors/custom-connectors/submit-certification).
+Connector certification is now included in ISV Studio, so you can use it to manage and track your connector certification submission. More information: [Submit your connector for Microsoft certification](https://docs.microsoft.com/connectors/custom-connectors/submit-certification)
 
-Before you start submitting your connector for certification, see the [Instructions on submitting your connector](https://docs.microsoft.com/connectors/custom-connectors/certification-submission) article for submission requirements.
+> [!NOTE]
+> Before you start submitting your connector for certification, see [Instructions on submitting your connector](https://docs.microsoft.com/connectors/custom-connectors/certification-submission) for submission requirements.
 
-To certify your custom connector through ISV Studio:
+**To certify your custom connector through ISV Studio**
 
-1. In ISV Studio, select **Connector certification** tab in the left pane.
-2. Select the type of connector to certify and click on **Submit**.
+1. In ISV Studio, select **Connector certification** in the leftmost pane.
+
+2. Select the type of connector to certify, and then select **Submit**.
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification](media/connector-certification-submit.png)
+   > ![Connector certification](media/connector-certification-submit.png "Connector certification")
 
-3. In the **Connector submission** page, read the agreement details and check the **Accept terms** and click on **Next**.
+3. On the **Connector submission** page, read the agreement details, select the **Accept terms** check box, and then select **Next**.
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification Consent form](media/connector-certification-consent-form.png)
+   > ![Consent form](media/connector-certification-consent-form.png "Consent form")
 
 4. Select **Choose a file** to upload the custom connector from your local machine. 
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification choose file](media/connector-certification-choose-file.png)
+   > ![Choose file](media/connector-certification-choose-file.png "Choose file")
 
-5. Enter the required details and click on **Submit for review**. 
+5. Enter the required details, and then select **Submit for review**. 
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification choose file](media/connector-certification-submit-for-review.png)
+   > ![Submit for review](media/connector-certification-submit-for-review.png "Submit for review")
 
-6. After you submit your connector for review, you'll receive an email from Microsoft.
+After you submit your connector for review, you'll receive an email from Microsoft.
 
-## See Also
+### See also
 
 [Home page](isv-app-management-homepage.md)<br/>
 [App page](isv-app-management-apppage.md)<br/>

powerapps-docs/developer/common-data-service/isv-app-management-certification.md

@@ -2,7 +2,7 @@
 title: "Use the QueryExpression class (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Use the QueryExpression class to build complex queries for use with the IOrganizationService.QueryBase) method or the RetrieveMultipleRequest message" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 04/17/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -21,18 +21,6 @@ In Common Data Service, you can use the <xref:Microsoft.Xrm.Sdk.Query.QueryExpre
 
  The <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> class lets you create complex queries. The <xref:Microsoft.Xrm.Sdk.Query.QueryByAttribute> class is designed to be a simple way to search for entities where attributes match specified values.  
 
- The following table lists the properties that you set to create a query expression.  
-  
-|Property|Description|  
-|--------------|-----------------|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.EntityName>|Specifies which type of entity will be retrieved. A query expression can only retrieve a collection of one entity type.|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.ColumnSet>|Specifies the set of attributes (columns) to retrieve.|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.Criteria>|Specifies complex conditional and logical filter expressions that filter the results of the query.|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.Distinct>|Specifies whether the results of the query contain duplicate records.|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.LinkEntities>|Specifies the links between multiple entity types.|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.Orders>|Specifies the order in which the records are returned from the query.|  
-|<xref:Microsoft.Xrm.Sdk.Query.QueryExpression.PageInfo>|Specifies the number of pages and the number of records per page returned from the query.|  
-  
 <a name="record_count"></a>   
 ## Record count  
  To find out how many records the query returned, set the <xref:Microsoft.Xrm.Sdk.Query.PagingInfo.ReturnTotalRecordCount> property to true before executing the query. When you do this, the <xref:Microsoft.Xrm.Sdk.EntityCollection.TotalRecordCount> will be set. Otherwise, this value will be -1.  
@@ -63,7 +51,25 @@ foreach (var a in result1.Entities)
 }  
 Console.WriteLine("---------------------------------------");  
 ```  
-  
+## Use SQL hints in a query
+
+The <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> class contains a property named <xref:Microsoft.Xrm.Sdk.Query.QueryExpression.QueryHints>. By setting this property to one of the supported string values shown below, you can provide a hint for generated SQL text which affects the query's execution.
+
+|QueryHint value | SQL Query Option and Hint |
+|---------|---------|
+|OptimizeForUnknown | Optimize For Unknown|
+|ForceOrder | Force Order |
+|Recompile | Recompile |
+|DisableRowGoal | use hint(‘Disable_Optimizer_RowGoal’) |
+|EnableOptimizerHotfixes | use hint('ENABLE_QUERY_OPTIMIZER_HOTFIXES') |
+|LoopJoin | Loop Join |
+|MergeJoin | Merge Join |
+|HashJoin | Hash Join |
+|NO_PERFORMANCE_SPOOL | NO_PERFORMANCE_SPOOL |
+|MaxRecursion | MAXRECURSION number |
+
+More information: [Hints (Transact-SQL) - Query](https://docs.microsoft.com/sql/t-sql/queries/hints-transact-sql-query)
+
 ### See also  
  [Building Queries with QueryExpression](build-queries-with-queryexpression.md)   
  [Use the ColumnSet Class](use-the-columnset-class.md)   

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

@@ -2,7 +2,7 @@
 title: "Get started with Common Data Service Web API (C#) (Common Data Service)| Microsoft Docs"
 description: "Learn how to access the Common Data Service Web API using the Microsoft Visual C# programming language"
 ms.custom: ""
-ms.date: 1/09/2019
+ms.date: 03/31/2020
 ms.service: powerapps
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -29,7 +29,9 @@ After completing this guide, you will have learned enough to explore the many ot
 
 ## In this section
 
-[Quick Start: Web API sample (C#)](quick-start-console-app-csharp.md)<br />
+[Quick Start: Web API sample](quick-start-console-app-csharp.md)  (Do this first)  
+[Enhanced quick start](enhanced-quick-start.md)  (Do this next)  
+[Start a Common Data Service Web API project in Visual Studio](start-web-api-project-visual-studio-csharp.md)
 
 ### See also
 

powerapps-docs/developer/common-data-service/webapi/get-started-dynamics-365-web-api-csharp.md

@@ -2,7 +2,7 @@
 title: "Use the Common Data Service Web API (Common Data Service)| Microsoft Docs"
 description: "The Common Data Service Web API implements OData v4 and provides a development experience that can be used across a wide variety of programming languages, platforms, and devices"
 ms.custom: ""
-ms.date: 04/22/2019
+ms.date: 03/31/2020
 ms.service: powerapps
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -28,14 +28,19 @@ The Web API is one of two web services you can use to work with data and metadat
 The Common Data Service Web API provides a development experience that can be used across a wide variety of programming languages, platforms, and devices. The Web API implements the OData (Open Data Protocol), version 4.0, an OASIS standard for building and consuming RESTful APIs over rich data sources. You can learn more about this protocol at [https://www.odata.org/](https://www.odata.org/). Details about this standard are available at [https://www.oasis-open.org/standards#odatav4.0](https://www.oasis-open.org/standards#odatav4.0). 
 
 
-Because the Web API is built on open standards, we don’t provide assemblies for a specific developer experience. You can compose HTTP requests for specific operations or use third-party libraries to generate classes for whatever language or platform you want. You can find a list of libraries that support OData version 4.0 at [https://www.odata.org/libraries/](https://www.odata.org/libraries/).  
+Because the Web API is built on open standards, we don't provide assemblies for a specific developer experience. You can compose HTTP requests for specific operations or use third-party libraries to generate classes for whatever language or platform you want. You can find a list of libraries that support OData version 4.0 at [https://www.odata.org/libraries/](https://www.odata.org/libraries/).  
 
 ## Web API and the Organization service
 
 It is valuable to recognize that the organization service is what defines the platform. The Web API provides a RESTful programming experience but ultimately all data operations go through the underlying organization service. The organization service defines the supported operations as messages. Each message has a name. These names are bound to the events used in the event framework to evaluate what registered extensions should be initiated. More information: [Event Framework](../event-framework.md)
 
 The Web API allows you to do all the same operations as the organization service but presents them in an RESTful style. OData v4 provides for named operations via *functions* or *actions*. Most messages available in the organization service are exposed as a corresponding named function or action. Those messages that correspond to CRUD operations are not available in the Web API because as a RESTful service they have implementations using GET, POST, PATCH, and DELETE HTTP methods, but within the platform the *retrieve*, *create*, *update*, and *delete* messages are invoked just as they are when the corresponding operations are performed using the .NET Framework assemblies.
 
+## Getting started
+
+Now that you have read an overview of the Web API, proceed to the [Get started with Common Data Service Web API](get-started-dynamics-365-web-api-csharp.md) topic to learn how to write your first C# program in Visual Studio that uses the Web API.
+
+If you are a JavaScript developer and want to use the Web API in model-driven apps, navigate to [Client-side JavaScript using Web API in model-driven apps](get-started-web-api-client-side-javascript.md).
 
 ### Related Sections