Merge branch 'master' into 2214778

Author: tapanm-MSFT

powerapps-docs/developer/data-platform/isv-app-management.md

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.reviewer: nabuthuk
 ms.workload: na
-ms.date: 02/11/2021
+ms.date: 04/11/2021
 ms.author: nabuthuk
 search.audienceType: 
   - developer
@@ -28,6 +28,9 @@ search.app:
 
 ISV Studio is designed to become the go-to Power Platform destination for Independent Software Vendors (ISV) to monitor and manage their applications. ISV Studio provides a consolidated cross tenant view of all the applications an ISV is distributing to customers.
 
+> [!div class="mx-imgBorder"]
+> ![Studio home page](media/isv-studio-home-page.png "Studio home page")
+
 [!INCLUDE[cc-terminology](includes/cc-terminology.md)]
 
 > [!IMPORTANT]
@@ -37,18 +40,23 @@ ISV Studio is designed to become the go-to Power Platform destination for Indepe
 
 ISV Studio supports applications built on the Microsoft Dataverse that are published to and deployed through [AppSource](https://appsource.microsoft.com/). No telemetry will be provided on side loaded solutions not deployed through AppSource.
 
-The applications currently available on the Dataverse includes Power Apps and Dynamics 365 for Sales, Marketing, Service, and Talent.
+The applications currently available on the Dataverse includes Power Apps and Dynamics 365 for Sales, Marketing, Service, and Talent. ISV Studio now provides telemetry features in Dynamics 365 Finance and Operations.
 
-As an end user installs an application from AppSource, a consent dialog will be displayed requesting the user to acknowledge that contact, usage, and transactional information may be shared with the application provider. This information is used by the provider to support billing and other transactional activities and to enable telemetry in ISV Studio for the ISV to learn from and act on.
+When end user installs an application from AppSource, a consent dialog will be displayed requesting the user to acknowledge that contact, usage, and transactional information may be shared with the application provider. This information is used by the provider to support billing and other transactional activities and to enable telemetry in ISV Studio for the ISV to learn from and act on.
 
 A customer can request that data not be shared with the provider, in which case Microsoft will remove all data from that particular tenant within ISV Studio.
 
 To access the public preview of ISV Studio, navigate your browser to [https://aka.ms/ISVStudio](https://aka.ms/ISVStudio/).
 
-## Pre-requisites
+## Pre-requisites for Microsoft Dataverse
 
 The ISV must be associated with a Microsoft registered Partner organization [ISV] that has one or more supported apps published in [AppSource](https://appsource.microsoft.com/). Supported apps include model-driven apps created using Power Apps and Dynamics 365 apps such as Dynamics 365 Sales and Dynamics 365 Customer Service.
 
+## Pre-requisites for Dynamics 365 Finance and Operations
+
+- For Dynamics 365 Finance and Operations, update the `SolutionID` in the descriptors with the `ProductId` of their offer in Partner Center. The `ProductId` of their offer can be found in the URL in Partner Center.
+- Ask customers to install the latest solution with the above. They need to be on version `10.0.16` or above to see the telemetry feature in ISV Studio.
+
 ### Admin access to ISV Studio
 
 To be an admin in ISV Studio,  your Azure Active Directory account must be configured as an app owner in Partner Center for their publisher account. Once you get the admin access, you'll be able to give more users access to ISV Studio from the studio directly.  
@@ -100,4 +108,4 @@ Please send an email to [[email protected]](mailto:ISVFeedback@microsoft
 [Publish your app on AppSource](publish-app-appsource.md)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/media/isv-studio-home-page.png

@@ -180,6 +180,9 @@ The Lucene query syntax supports the following functionality:
 | Proximity search                  | Returns results where terms are within *x* words of each other, for more contextual results.<br/>For example, "airport hotel"\~5 returns results where "airport" and "hotel" are within five words of each other, thus boosting the chances of finding a hotel located close to an airport. |
 | Regular expression (regex) search | For example, /\[mh\]otel/ matches "motel" or "hotel". |
 
+> [!NOTE]
+> Wildcards are used only for word completion in Relevance Search. As a rule, querying with a leading wildcard will take significantly longer than not using a wildcard, so we encourage you to explore alternative ways to find what you're looking for and only use leading wildcards sparingly, if at all.
+
 In order to use any of the search operators as part of the search text, escape the character by prefixing it with a single backslash (\\). Special characters that require escaping include the following: + - & | ! ( ) { } [ ] ^ " ~ * ? : \ /
 
 ### Example: basic search
@@ -523,4 +526,4 @@ POST [Organization URI]/api/search/v1.0/autocomplete
 [Connect with your Dataverse environment](setup-postman-environment.md#connect-with-your-dataverse-environment)
 
 
-[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/webapi/relevance-search.md

@@ -210,12 +210,12 @@ This data is also available for you to browse using the [Power Platform Admin Ce
 ### See also
 
 [Write plug-ins to extend business processes](plug-ins.md)<br />
-[Best practices and guidance regarding plug-in and workflow development](best-practices/business-logic/index.md)
+[Best practices and guidance regarding plug-in and workflow development](best-practices/business-logic/index.md)<br />
 [Handle exceptions](handle-exceptions.md)<br />
 [Impersonate a user](impersonate-a-user.md)<br />
 [Tutorial: Write and register a plug-in](tutorial-write-plug-in.md)<br />
 [Tutorial: Debug a plug-in](tutorial-debug-plug-in.md)<br />
 [Tutorial: Update a plug-in](tutorial-update-plug-in.md)<br />
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

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

@@ -23,8 +23,6 @@ search.app:
 ---
 # Build Windows client applications using the XRM tools
 
-[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
-
 XRM tooling is a set of APIs built on top of the Microsoft Dataverse assembly APIs (Organization service and Discovery service) that provide support for building Windows client applications for Dataverse. It provides the following capabilities:  
 
 - Supports all the authentication modes to sign in to Dataverse instance.  

powerapps-docs/developer/data-platform/xrm-tooling/build-windows-client-applications-xrm-tools.md

@@ -23,8 +23,6 @@ search.app:
 ---
 # Configure tracing for XRM tooling
 
-[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
-
 You can enable tracing to record data related to process milestones across all components of XRM tooling, such as operation calls, warnings, exceptions, and other significant events. This information can be used for troubleshooting operational and performance issues in your Windows client applications. Tracing in XRM tooling is built on top of [System.Diagnostics.Tracing](/dotnet/api/system.diagnostics.tracing). To enable tracing for an assembly or component, for example Microsoft.Xrm.Tooling.Connector, you must define the following three things for each component in your code or in the application configuration file (*\<AppName>*.exe.config):  
 
 - A trace source  

powerapps-docs/developer/data-platform/xrm-tooling/configure-tracing-xrm-tooling.md

@@ -1,8 +1,8 @@
 ---
 title: "Sample: Quick start for XRM Tooling API (Microsoft Dataverse)| Microsoft Docs"
-description: ""
+description: "This code sample demonstrates how to connect to a Microsoft Dataverse environment by using the XRM Tooling APIs, and then perform basic create, update, retrieve, and delete operations on a table"
 ms.custom: ""
-ms.date: 03/27/2019
+ms.date: 04/12/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.suite: ""
@@ -23,9 +23,9 @@ search.app:
 ---
 # Sample: Quick start for XRM Tooling API
 
-[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
+[!INCLUDE[cc-terminology](../includes/cc-terminology.md)]
 
-The QuickStart sample is a .NET Framework managed code sample that shows how to connect to a Microsoft Dataverse instance by using the XRM Tooling APIs, and perform basic create, update, retrieve, and delete operations on an entity. For more information about XRM Tooling, see [Build windows client applications using the XRM tools](build-windows-client-applications-xrm-tools.md).
+The QuickStart sample is a .NET Framework managed code sample that shows how to connect to a Microsoft Dataverse instance by using the XRM Tooling APIs, and perform basic create, update, retrieve, and delete operations on a table. For more information about XRM Tooling, see [Build windows client applications using the XRM tools](build-windows-client-applications-xrm-tools.md).
 
 Download the sample: [Work with XRM Tooling API](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/Xrm%20Tooling/Quick%20start%20for%20XRM%20Tooling%20API)
 
@@ -40,7 +40,7 @@ Download the sample: [Work with XRM Tooling API](https://github.com/microsoft/Po
 
 - The sample code is built using the **WPF Application for CRM** SDK template that provides a common login control with built-in support for authentication and credential caching and reuse. For more information about the common login control and how to use the SDK template in Visual Studio, see [Use the XRM Tooling common login control](use-xrm-tooling-common-login-control-client-applications.md).  
 - No helper code is used to establish a connection to Dataverse.  
-- After connecting to Dataverse, the sample performs basic create, update, retrieve, and delete operations on an account entity.  
+- After connecting to Dataverse, the sample performs basic create, update, retrieve, and delete operations on an account table.  
 - Stores user credentials in a configuration file (`Default_QuickStartXRMToolingWPFClient.exe.config`) in the `c:\Users\`*`<username>`*`\AppData\Roaming\Microsoft\QuickStartXRMToolingWPFClient` folder when the sample is run for the first time, and thereafter prompts the user to either use the stored or specify new credentials at runtime to sign in to Dataverse.  
 - Generates the following log files, if any issue occurs, to aid troubleshooting:  
 - Login_ErrorLog.log: To report sign-in errors. This file is available at `C:\Users\`*`<username>`*`\AppData\Roaming\Microsoft\QuickStartXRMToolingWPFClient`.  

powerapps-docs/developer/data-platform/xrm-tooling/sample-quick-start-xrm-tooling-api.md

@@ -1,8 +1,8 @@
 ---
 title: "Sample: Simplified connection quick start (Developer Guide for Microsoft Dataverse) | MicrosoftDocs"
-description: "This sample shows you how to connect to the Microsoft Dataverse web services using the CrmServiceClient and perform basic create, update, retrieve, and delete operations on an entity. "
+description: "This sample shows you how to connect to the Microsoft Dataverse web services using the CrmServiceClient and perform basic create, update, retrieve, and delete operations on a table. "
 ms.custom: 
-ms.date: 03/27/2019
+ms.date: 04/12/2021
 author: Nkrb
 ms.service: powerapps
 ms.suite: 
@@ -22,9 +22,9 @@ search.app:
 ---
 # Sample: Simplified connection quick start using Microsoft Dataverse
 
-[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
+[!INCLUDE[cc-terminology](../includes/cc-terminology.md)]
 
-This sample shows how to connect to the Dataverse web services using the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> and perform basic create, update, retrieve, and delete operations on an entity. For more information about the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient>, see [Use CrmServiceClient constructors to connect to Dataverse](use-crmserviceclient-constructors-connect.md).
+This sample shows how to connect to the Dataverse web services using the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> and perform basic create, update, retrieve, and delete operations on a table. For more information about the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient>, see [Use CrmServiceClient constructors to connect to Dataverse](use-crmserviceclient-constructors-connect.md).
 
 ## Requirements
 
@@ -34,13 +34,13 @@ You must modify the `app.config` file with connection information for your Datav
 
 ## Demonstrates
 
-This sample authenticates the user with the Dataverse web services by using the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> and methods. After obtaining a reference to the Organization web service, the sample performs basic create, update, retrieve, and delete operations on an `account` entity. The sample also handles common exceptions. No helper code is used to establish a connection to the Organization web service.  
+This sample authenticates the user with the Dataverse web services by using the <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> and methods. After obtaining a reference to the Organization web service, the sample performs basic create, update, retrieve, and delete operations on an `account` table. The sample also handles common exceptions. No helper code is used to establish a connection to the Organization web service.  
 
 In addition, this sample supports `OAuth` authentication and advanced connection diagnostics. For more information on using diagnostics, see [Configure tracing for XRM Tooling](configure-tracing-xrm-tooling.md).
 
 ## Example
 
-The following shows a sample `app.config file`. To use this, remove the comment characters “<!- -” at the beginning of the \<add … /> line and the “- ->” at the end on the line for the line that is relevant to your server and organization. Next, modify the attribute values as appropriate for your configuration.
+The following shows a sample `app.config file`. To use this, remove the comment characters “<!- -” at the beginning of the \<add … /> line and the “- ->” at the end on the line for the line that is relevant to your server and organization. Next, modify the data values as appropriate for your configuration.
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>  

powerapps-docs/developer/data-platform/xrm-tooling/sample-simplified-connection-quick-start.md

@@ -2,7 +2,7 @@
 title: "Sample: Task Parallel Library with CrmServiceClient (Microsoft Dataverse)| Microsoft Docs"
 description: "Task Parallel Library (TPL) makes developers more productive by simplifying the process of adding parallelism and concurrency to applications. This sample demonstrates using this with CrmServiceClient"
 ms.custom: ""
-ms.date: 04/20/2020
+ms.date: 04/12/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.suite: ""
@@ -21,7 +21,7 @@ search.app:
 ---
 # Sample: Task Parallel Library with CrmServiceClient
 
-[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
+[!INCLUDE[cc-terminology](../includes/cc-terminology.md)]
 
 Task Parallel Library (TPL) makes developers more productive by simplifying the process of adding parallelism and concurrency to applications.
 
@@ -43,9 +43,9 @@ More information: [Service Protection API Limits](../api-limits.md)
 
 The [CrmServiceClient.Clone Method](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient.clone) enables TPL to use the client with multiple threads.
 
-This simple sample will generate a number of account entity records using the [System.Threading.Tasks.Parallel.ForEach Method](/dotnet/api/system.threading.tasks.parallel.foreach).
+This simple sample will generate a number of account table records using the [System.Threading.Tasks.Parallel.ForEach Method](/dotnet/api/system.threading.tasks.parallel.foreach).
 
-Then it will use that technique again to delete the entities created.
+Then it will use that technique again to delete the tables created.
 
 **NOTE**:
 > By default, this sample will create only 10 records, which is not enough to hit the service protection api limit errors. If you raise the `numberOfRecords` variable value to 10000, you can use Fiddler to observe how some of the requests will be rejected and re-tried.
@@ -278,5 +278,4 @@ private static void DeleteEntities(CrmServiceClient svc, List<EntityReference> e
 
 [Task Parallel Library (TPL)](/dotnet/standard/parallel-programming/task-parallel-library-tpl)
 
-
 [!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/xrm-tooling/sample-tpl-crmserviceclient.md

@@ -17,8 +17,6 @@ search.app:
 ---
 # Use connection strings in XRM tooling to connect to Microsoft Dataverse
 
-[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
-
 With Dataverse, XRM tooling enables you to connect to your Dataverse environment by using connection strings. This is similar to the concept of connection strings used with **SQL Server**. Connection strings have native support in configuration files, including the ability to encrypt the configuration sections for maximum security. This enables you to configure Dataverse connections at deployment time, and not hard code in your application to connect to your Dataverse environment.