Merge branch 'master' into pehecke-aad-security

Author: phecke

powerapps-docs/developer/data-platform/configure-entity-relationship-cascading-behavior.md

@@ -50,8 +50,9 @@ The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguratio
 |UserOwned|Cascade User Owned|Perform the action on all referencing table records owned by the same user as the referenced table record.|  
 
 >[!NOTE]
-> Cascading actions on Active records will only include records that have a Status Code of Active. Any other solution provided or custom status 
-> codes that indicate a record as live and in use will not be processed as an Active record for cascading purposes.
+> Cascading actions on active records will only include records that have a state code of "Active" and a status code of "Open". 
+> If custom status and state code labels are being used, this is the same as `statecode` value=0 and `statuscode` value=1 in most cases. 
+> Any other solution provided or custom status codes with values other than the above will not be processed as an active record for cascading purposes.
 
 
  The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguration> class or <xref href="Microsoft.Dynamics.CRM.CascadeConfiguration?text=CascadeConfiguration ComplexType" />) contains the following properties representing actions that may be performed on the referenced table in the one-to-many relationship.  

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

@@ -1,6 +1,6 @@
 ---
 title: "Data Synchronization (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "Sometimes you’ll need to synchronize and integrate Microsoft Dataverse data with data that is stored in other systems. The common data integration patterns include taking data from an external system and pushing it into Dataverse, taking data from Dataverse and synchronizing it to some external data store, or updating Dataverse with external data. You can now use several new capabilities to make it easier to write code to achieve these scenarios." # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Learn about synchronizing Dataverse data with external systems." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 03/24/2021
 ms.reviewer: "pehecke"

powerapps-docs/developer/data-platform/deployment-service/administer-deployment-using-deployment-web-service.md

@@ -1,6 +1,6 @@
 ---
 title: "Administer the deployment using the deployment web service (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "<Description>" # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Learn about the deployment web service." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"

powerapps-docs/developer/data-platform/developer-resources-page.md

@@ -1,6 +1,6 @@
 ---
 title: "Developer resources page (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "<Description>" # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Learn about the developer resources web page." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"

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

@@ -1,6 +1,6 @@
 ---
 title: "On-premises deployment options (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "<Description>" # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Learn about deployment options for an on-premise installation." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"

powerapps-docs/developer/data-platform/on-premises-options.md

@@ -53,6 +53,8 @@
     href: entity-operations-update-delete.md
   - name: Associate and disassociate entities
     href: entity-operations-associate-disassociate.md
+  - name: Access entity data faster using partitions
+    href: azure-storage-partitioning-sdk.md
 - name: Use messages
   href: use-messages.md
 - name: Special Operations

powerapps-docs/developer/data-platform/org-service/TOC.yml

@@ -0,0 +1,101 @@
+---
+title: "Improve performance using storage partitions when accessing entity data (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "Learn how to improve performance when accessing non-relational entity date." # 115-145 characters including spaces. This abstract displays in the search result.
+ms.custom: ""
+ms.date: 01/25/2021
+ms.reviewer: "pehecke"
+ms.service: powerapps
+ms.topic: "article"
+author: "JimDaly" # GitHub ID
+ms.author: "pehecke" # MSFT alias of Microsoft employees only
+manager: "sunilg" # MSFT alias of manager or PM counterpart
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+# Improve performance using storage partitions when accessing entity data
+
+An optional partition key can be specified to create a logical partition for non-relational custom entity data stored in NoSql tables of Azure heterogenous storage ([Cosmos DB](/azure/cosmos-db/introduction)). Having a partition key improves application performance for large sets of data (millions of records) by grouping data items into logical sets within a table. For example, a table containing products can be grouped logically into product categories to improve retrieval of all items within a product category. The partition key value can be a string or numeric type. Once specified, the partition key value can't be changed.
+
+When no partition key is specified, the table is the logical boundary and retrieving a single item or a set of logically related items from a large data set will not be as performant as when using a partition key.
+
+## Creating and accessing a partition
+
+A unique new partition key value must be used to create a new logical partition. The same value must be used to create additional items in the same logical partition and to retrieve, update, or delete items belonging to that logical partition.
+
+```csharp
+public void Run(CrmServiceClient client)
+{
+    // Create
+    Entity entity = new Entity("new_msdyn_customer");
+    entity["new_firstname"] = "Monica";
+    entity["new_lastname"] = "Thompson";
+
+    // First use of the partition ID value during an entity Create operation
+    // also creates the partition where that entity record is stored.
+    entity["partitionid"] = "CustomerPartition"; 
+    Guid id = client.Create(entity); 
+
+    // Update
+    UpdateRequest updateRequest = new UpdateRequest();
+    entity = new Entity("new_msdyn_customer", id);
+    entity["new_firstname"] = "Cora";
+    //entity["new_lastname"] = "Thomas";
+    entity["partitionid"] = "CustomerPartition";
+    updateRequest.Target = entity;
+    var updateResponse = (UpdateResponse)client.Execute(updateRequest);
+
+    // Retrieve
+     RetrieveRequest request = new RetrieveRequest();
+     request.ColumnSet = new ColumnSet("new_firstname");
+     request.Target = new EntityReference("new_msdyn_customer", id);
+     request["partitionId"] = "CustomerPartition";
+     var response = (RetrieveResponse)client.Execute(request);
+
+     // RetrieveMultiple
+     RetrieveMultipleRequest retreiveMultipleRequest = new RetrieveMultipleRequest();
+     retreiveMultipleRequest.Query = new QueryExpression()
+     {
+         EntityName = "new_msdyn_customer",
+         ColumnSet = new ColumnSet("new_firstname")
+     };
+     retreiveMultipleRequest["partitionId"] = "CustomerPartition";
+     var retrieveResponse = (RetrieveMultipleResponse)client.Execute(retreiveMultipleRequest);
+
+     // Update and insert
+     UpsertRequest upsertRequest = new UpsertRequest();
+     entity = new Entity("new_msdyn_customer", id);
+     entity["new_firstname"] = "Andre";
+     entity["new_lastname"] = "Lawson";
+     entity["partitionid"] = "CustomerPartition";
+     upsertRequest.Target = entity;
+     var upsertResponse = (UpsertResponse)client.Execute(upsertRequest);
+
+     // Delete
+     DeleteRequest deleteRequest = new DeleteRequest();
+     deleteRequest.Target = new EntityReference("new_msdyn_customer", id);
+     deleteRequest["partitionId"] = "CustomerPartition";
+     var deleteResponse = (DeleteResponse)client.Execute(deleteRequest);
+}
+```
+
+## Additional information
+
+Here are a few more details about the partition key and partition management.
+
+- The key value must be unique in the environment.
+- A partition is limited to 20 GB of data, and there is no method available to check the partition's current size.
+- There is no defined limit to the number of partitions you can allocate in an environment.
+- Partition allocation is automatic. Specifying a unique partition key during a Create operation creates a partition. When all data has been deleted from the partition, the partition is automatically deleted.
+- There is no method available to rename a key.
+- Presently, only the Create, Update, Retrieve, and Delete entity operations support storage partitioning.
+
+### See Also
+
+[Passing optional parameters with a request](use-messages.md#passing-optional-parameters-with-a-request)  
+[Create entities using the Organization Service](entity-operations-create.md)  
+[Retrieve an entity using the Organization Service](entity-operations-retrieve.md)  
+[Update and Delete entities using the Organization Service](entity-operations-update-delete.md)  
+[Partitioning and horizontal scaling in Azure Cosmos DB](/azure/cosmos-db/partitioning-overview)

powerapps-docs/developer/data-platform/org-service/azure-storage-partitioning-sdk.md

@@ -1,6 +1,6 @@
 ---
 title: "Create entities using the Organization Service (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "<Description>" # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Learn how to create entities using the Organization Service." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"
@@ -272,6 +272,10 @@ Another way to create an entity is by using the <xref:Microsoft.Xrm.Sdk.Messages
 
 More information: [Use Upsert](entity-operations-update-delete.md#use-upsert)
 
+## Create documents in storage partitions
+
+If you are creating large numbers of entities that contain documents, you can create the entities in storage partitions to speed up access to those entity records. More information: [Improve performance when accessing documents using storage partitions](azure-storage-partitioning-sdk.md)
+
 
 ### See also