Merge branch 'main' into noa-agent-builder

Author: mduelae

powerapps-docs/developer/data-platform/org-service/entity-operations-associate-disassociate.md

@@ -1,7 +1,7 @@
 ---
 title: "Associate and disassociate table rows using the SDK for .NET (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to associate and disassociate table rows using the SDK for .NET" # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 03/22/2022
+ms.date: 12/13/2024
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: MicroSri
@@ -19,9 +19,9 @@ contributors:
 
 Table rows are associated to each other using lookup columns on the related table row. The simplest way to associate two rows in a one-to-many relationship is to use an <xref:Microsoft.Xrm.Sdk.EntityReference> to set the value of a lookup column on the related row.
 
-The simplest way to disassociate two rows in a one-to-many relationship is to set the value of the lookup column to null.
+The simplest way to disassociate two rows in a one-to-many relationship is to set the value of the lookup column to `null`.
 
-Relationships using an many-to-many relationship also depend on lookup columns on the *intersect entity* that supports the many-to-many relationship. These relationship are defined by the existence of rows in that intersect entity. While you can interact with the intersect entity directly, it is much easier to use the API to do this for you.
+Relationships using a many-to-many relationship also depend on lookup columns on the *intersect entity* that supports the many-to-many relationship. Relationship are defined by the existence of rows in that intersect entity. While you can interact with the intersect entity directly, it's much easier to use the API to do this task for you.
 
 ## Use the Associate method or AssociateRequest
 
@@ -40,109 +40,49 @@ Whether the relationship is a one-to-many or many-to-many relationship doesn't m
 
 You can discover the names of the relationships by viewing the customization UI or in the metadata using the Metadata Browser.
 
-More information: 
+More information:
 
 - [Create and edit 1:N (one-to-many) or N:1 (many-to-one) relationships](../../../maker/data-platform/create-edit-1n-relationships.md)
 - [Create and edit many-to-many (N:N) table row relationships](../../../maker/data-platform/create-edit-nn-relationships.md)
 - [Browse the metadata for your environment](../browse-your-metadata.md)
 
-The following example will set a specific contact (`jimGlynn`) as the primary contact for all accounts that are in Redmond.
+The following example creates a relationship and associates a primary entity with a collection of related entities.
 
+:::code language="csharp" source="~/../PowerApps-Samples/dataverse/orgsvc/CSharp-NETCore/Relationships/AssociateDisassociate/Program.cs" id="AssociateDisassociate":::
+Complete code sample: [AssociateDisassociate](https://github.com/microsoft/PowerApps-Samples/blob/master/dataverse/orgsvc/CSharp-NETCore/Relationships/AssociateDisassociate/Program.cs)
 
-```csharp
-
-// Retrieve the accounts
-var query = new QueryByAttribute("account")
-{
-ColumnSet = new ColumnSet("name")
-};
-query.AddAttributeValue("address1_city", "Redmond");
-
-EntityCollection accounts = svc.RetrieveMultiple(query);
-
-//Convert the EntityCollection to a EntityReferenceCollection
-var accountReferences = new EntityReferenceCollection();
-
-accounts.Entities.ToList().ForEach(x => {
-accountReferences.Add(x.ToEntityReference());
-});
-
-// The contact to associate to the accounts
-var jimGlynn = new EntityReference("contact", 
-new Guid("cf76763a-ba1c-e811-a954-000d3af451d6"));
-
-// The relationship to use
-var relationship = new Relationship("account_primary_contact");
-
-// Use the Associate method
-svc.Associate(jimGlynn.LogicalName, jimGlynn.Id, relationship, accountReferences);
-```
-Although there is no particular advantage in doing so, if you wanted to use the <xref:Microsoft.Xrm.Sdk.Messages.AssociateRequest>, you can replace the last line with this:
-
+If you wanted to use the <xref:Microsoft.Xrm.Sdk.Messages.AssociateRequest>, you would use the following code. A benefit of using the request instead of the service client method is that the request supports the [use of optional parameters](../optional-parameters.md).
 
 ```csharp
-// Use AssociateRequest
 AssociateRequest request = new AssociateRequest()
 {
-RelatedEntities = accountReferences,
-Relationship = relationship,
-Target = jimGlynn
+RelatedEntities = relatedEntities,
+Relationship = relation,
+Target = primaryEntity
 };
 
-svc.Execute(request);
+service.Execute(request);
 ```
 
-This operation is the same as three separate update operations to the [Account](../reference/entities/account.md).[PrimaryContactId](../reference/entities/account.md#BKMK_PrimaryContactId) lookup column, but it is using the [account_primary_contact](../reference/entities/contact.md#BKMK_account_primary_contact) relationship, which is a many-to-one entity relationship on the account and a one-to-many entity relationship on the contact.
+Let's say we are associating a primary entity (a contact) with three related entities (accounts). This single association operation shown above is the same as three separate update operations where the [Account](../reference/entities/account.md).[PrimaryContactId](../reference/entities/account.md#BKMK_PrimaryContactId) lookup column is set. Instead, the simpler service client method or request call is using the [account_primary_contact](../reference/entities/contact.md#BKMK_account_primary_contact) relationship which establishes a many-to-one entity relationship on each related account and a one-to-many entity relationship on the contact.
 
 If you examine the properties of the relationship columns, you can see that the `ReferencingEntity` value is `account` and the `ReferencingAttribute` value is `primarycontactid`.
 
-
 ## Use the Disassociate method or DisassociateRequest
 
 The <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Disassociate*> method or the <xref:Microsoft.Xrm.Sdk.Messages.DisassociateRequest> with the <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*> method are just the reverse of the way that you associate table rows.
 
-The following code reverses the associations made in the sample above.
-
-
-```csharp
-// Retrieve the accounts
-var query = new QueryByAttribute("account")
-{
-ColumnSet = new ColumnSet("name")
-};
-query.AddAttributeValue("address1_city", "Redmond");
-
-EntityCollection accounts = svc.RetrieveMultiple(query);
-
-//Convert the EntityCollection to a EntityReferenceCollection
-var accountReferences = new EntityReferenceCollection();
-
-accounts.Entities.ToList().ForEach(x => {
-accountReferences.Add(x.ToEntityReference());
-});
-
-// The contact to associate to the accounts
-var jimGlynn = new EntityReference("contact", 
-new Guid("cf76763a-ba1c-e811-a954-000d3af451d6"));
-
-// The relationship to use
-var relationship = new Relationship("account_primary_contact");
-
-// Use the Disassociate method
-svc.Disassociate(jimGlynn.LogicalName, jimGlynn.Id, relationship, accountReferences);
-```
-Although there is no particular advantage in doing so, if you wanted to use the <xref:Microsoft.Xrm.Sdk.Messages.DisassociateRequest>, you can replace the last line with this:
+You can view an example `Disassociate` method call in the previously shown code sample. If you wanted to use the <xref:Microsoft.Xrm.Sdk.Messages.DisassociateRequest>, the code would look like this:
 
 ```csharp
-// Use DisassociateRequest
 DisassociateRequest request = new DisassociateRequest()
 {
-RelatedEntities = accountReferences,
-Relationship = relationship,
-Target = jimGlynn
+RelatedEntities = relatedEntities,
+Relationship = relation,
+Target = primaryEntity
 };
 
-svc.Execute(request);
+service.Execute(request);
 ```
 
 ### See also

powerapps-docs/developer/data-platform/org-service/samples/work-activity-party-records.md

@@ -18,7 +18,7 @@ contributors:
 This sample code shows how to work with activity party records.
 
 > [!div class="nextstepaction"]
-> [SDK for .NET: Work with activity party records sample code](https://github.com/microsoft/PowerApps-Samples/tree/master/dataverse/orgsvc/CSharp/ActivityPartyRecords)
+> [SDK for .NET: Work with activity party records sample code](https://github.com/microsoft/PowerApps-Samples/tree/master/dataverse/orgsvc/CSharp-NETCore/Activities/ActivityParty)
 
 ## How to run this sample
 

powerapps-docs/maker/TOC.yml

@@ -1336,6 +1336,8 @@
     items:
     - name: Overview
       href: ./canvas-apps/create-performant-apps-overview.md
+    - name: Use Monitor to get insights and recommendations (preview)
+      href: ./canvas-apps/monitor-app-performance.md  
     - name: Understand canvas app execution phases and data flow
       href: ./canvas-apps/execution-phases-data-flow.md
     - name: Small data payload

powerapps-docs/maker/canvas-apps/media/intro-maker-portal/pin-button.png

@@ -0,0 +1,63 @@
+---
+title: Monitor your canvas apps performance (preview)
+description: Get valuable insights and recommendations for your canvas app using Monitor.
+author: dalajogun
+ms.topic: conceptual
+ms.custom: canvas
+ms.reviewer: mkaur
+ms.date: 11/18/2024
+ms.subservice: canvas-maker
+ms.author: damialajogun
+search.audienceType: 
+  - maker
+contributors:
+  - mduelae
+  - damialajogun
+---
+#  Use Monitor to get insights and recommendations for your canvas app (preview)
+
+Monitor in Power Apps offers insights and recommendations to enhance app performance. It provides makers with detailed information on their app's performance and actionable steps to improve their apps.
+
+> [!IMPORTANT]
+>
+> - This is a preview feature.
+> - Preview features aren't meant for production use and might have restricted functionality. These features are subject to [supplemental terms of use](https://go.microsoft.com/fwlink/?linkid=2189520), and are available before an official release so that customers can get early access and provide feedback.
+> - This feature is being gradually rolled out across regions and might not be available yet in your region.
+
+## Prerequisites
+
+To use this feature, your administrator must enable certain analytics and monitoring settings in the Power Platform Admin Center. More information: [Monitoring experiences for makers](/power-platform/admin/monitoring/monitoring-overview#monitoring-experiences-for-makers)
+
+## Open and pin Monitor
+
+1. Sign in to [Power Apps](https://make.powerapps.com).
+1. On the left navigation, select **Apps**.
+1. On the command bar, select **Monitor**.
+1. On the left navigation pane, select the ![Pin button.](media/intro-maker-portal/pin-button.png) pin button next to **Monitor**.
+
+
+## Use Monitor 
+
+The **Monitor** page displays metric cards at the top, highlighting the top three underperforming apps for each metric. If all apps perform well on a specific metric, then no apps are listed in the card.
+
+:::image type="content" source="media/monitor-apps/monitor-screen.png" alt-text="Monitor main screen showing app metrics":::
+
+| Metric | Definition |
+| ------------- | ------------- |
+| **App open success rate**  | Indicates the percentage of app launch attempts that successfully allowed end-users to access the app. This metric is calculated once every 24 hours.|
+| **Time to interact**  | Measures the time end-users wait to access the first screen of an app. It doesn't include the time users wait to see all data presented on the first screen, such as filling in rows of a gallery. This metric is calculated every 24 hours and is measured using percentiles, with the 75th percentile being reported. |
+| **Time to full load**  | Measures the time end-users wait to see all data displayed on the first screen of an app. In the app launch lifecycle, this metric follows the **Time to interact** phase. This metric is calculated every 24 hours and is measured using percentiles, with the 75th percentile being reported.|
+
+
+### View metrics and recommendations for an app
+
+  When you select an app on the  **Monitor** page a side pane opens and display more data for each metric, including a data chart for the last 30 days.
+
+1. On **Monitor** page, select an app.
+
+1. To view recommendations for an app, select the app’s name to open the side panel. The chart shows a callout with a recommended action for improving the metric.
+
+    :::image type="content" source="media/monitor-apps/monitor-side-pane.png" alt-text="App metrics and recommendations":::
+
+  > [!IMPORTANT]
+  > Recommendations are only available in Managed Environments. Please contact your admin to enable Managed Environments for access to recommendations.