Merge branch 'main' into ericcolvinmorgan/dual-write-updates

Author: Mattp123

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

@@ -126,6 +126,9 @@
       items:
         - name: Use DeleteMultiple (preview)
           href: deletemultiple.md
+    - name: Restore deleted records (preview)
+      displayName: RecycleBin, Restore
+      href: restore-deleted-records.md
     - name: Create your own messages
       href: custom-actions.md
       items:

powerapps-docs/developer/data-platform/restore-deleted-records.md

@@ -17,7 +17,7 @@ contributors:
 ---
 # Custom column analyzers for Dataverse Search
 
-Dataverse search uses many different [Azure AI Search](/azure/search/search-what-is-azure-search) capabilities that include both index and search analyzers to return the best data based on what the user asks for. These built-in capabilities to help define how an index maps certain phrases or words to the best match to data in a column and a row in a table.
+Dataverse search uses many different [Azure AI Search](/azure/search/search-what-is-azure-search) capabilities that include both index and search analyzers to return the best data based on what the user asks for. These built-in capabilities help to define how an index maps certain phrases or words to the best match to data in a column and a row in a table.
 
 Examples include search strings that have special characters, or frequently used words (like '`of`' and '`or`')  that the back-end data engine removes from the search term when the query is processed.
 

powerapps-docs/developer/data-platform/search/custom-search-analyzer.md

@@ -0,0 +1,170 @@
+---
+title: "Web API table schema operations sample (PowerShell) (Microsoft Dataverse)| Microsoft Docs"
+description: "This sample demonstrates how to perform operations that change the Dataverse data structures using the Web API with PowerShell."
+ms.date: 05/14/2024
+author: mkannapiran
+ms.author: kamanick
+ms.reviewer: jdaly
+search.audienceType: 
+  - developer
+contributors: 
+  - JimDaly
+---
+
+# Web API table schema operations sample (PowerShell)
+
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
+This PowerShell sample demonstrates how to perform operations that create and modify table, column, and relationship definitions using the Dataverse Web API.
+  
+This sample implements the Dataverse operations and console output detailed in [Web API table schema operations sample](../web-api-metadata-operations-sample.md) and uses the [Dataverse Web API PowerShell Helper functions](https://github.com/microsoft/PowerApps-Samples/blob/master/dataverse/webapi/PS/README.md) to manage authentication and provide reusable functions to perform common operations. These scripts are referenced using [dot sourcing](/powershell/module/microsoft.powershell.core/about/about_scripts#script-scope-and-dot-sourcing) with the following lines:
+
+```powershell
+. $PSScriptRoot\..\Core.ps1
+. $PSScriptRoot\..\TableOperations.ps1
+. $PSScriptRoot\..\CommonFunctions.ps1
+. $PSScriptRoot\..\MetadataOperations.ps1
+```
+
+> [!NOTE]
+> This sample should work with Windows, Linux, and macOS, but has only been tested on Windows.
+  
+## Prerequisites
+
+Before running this sample, you should read these articles that explain concepts and patterns used by these samples:
+
+- [Quick Start Web API with PowerShell and Visual Studio Code](../quick-start-ps.md)
+- [Use PowerShell and Visual Studio Code with the Dataverse Web API](../use-ps-and-vscode-web-api.md)
+
+These articles have the same prerequisites.
+
+[!INCLUDE [cc-visual-studio-code-powershell-prerequisites](../../includes/cc-visual-studio-code-powershell-prerequisites.md)]
+  
+## How to run this sample
+
+1. Clone or download the [PowerApps-Samples](https://github.com/microsoft/PowerApps-Samples) repository.
+1. Open the `/dataverse/webapi/PS/MetadataOperations/MetadataOperationsSample.ps1` file using Visual Studio Code
+1. Edit this line to use the URL of the environment you want to connect to:
+
+   `Connect 'https://yourorg.crm.dynamics.com/' # change this`
+
+1. (Optional) Set the `$deleteCreatedRecords` variable to `$false` if you don't want to delete the records this sample creates.
+1. Press <kbd>F5</kbd> to run the sample.
+1. The first time you run the sample a browser window opens. In the browser window, enter or select the credentials you want to use to authenticate.
+
+To connect as a different user, run the [Disconnect-AzAccount command](/powershell/module/az.accounts/disconnect-azaccount) and try again.
+
+## Code
+
+The code for this sample is at: [PowerApps-Samples/dataverse/webapi/PS/MetadataOperations/MetadataOperationsSample.ps1](https://github.com/microsoft/PowerApps-Samples/blob/master/dataverse/webapi/PS/MetadataOperations/MetadataOperationsSample.ps1)
+
+## Demonstrates
+
+This sample has 11 regions:
+
+### Section 0: Create Publisher and Solution
+
+Operations: Create a solution record and an associated publisher record.
+
+> [!NOTE]
+> All solution components created in this sample will be associated to the solution so that they can be exported. For operations without a named message, this association is created using the `MSCRM.SolutionUniqueName` request header setting the solution unique name set as the value.
+> All names of solution components are prefixed using the publisher customization prefix.
+
+### Section 1: Create, Retrieve and Update Table
+
+Operations:
+
+1. Create a new `sample_BankAccount` user-owned table by sending a `POST` request to `/EntityDefinitions`.
+1. Retrieve the created table by sending a `GET` request to `/EntityDefinitions(LogicalName='sample_bankaccount')`.
+1. Update the table by sending a `PUT` request to `/EntityDefinitions(LogicalName='sample_bankaccount')`.
+
+### Section 2: Create, Retrieve and Update Columns
+
+Operations:
+
+1. Attempt to retrieve a `sample_boolean` boolean column by sending a `GET` request to `/EntityDefinitions(LogicalName='sample_bankaccount')/Attributes(LogicalName='sample_boolean')`.
+1. If the column doesn't already exist, create a new `sample_boolean` boolean column for the `sample_BankAccount` table by sending a `POST` request to `/EntityDefinitions(LogicalName='sample_bankaccount')/Attributes`.
+1. Update the `sample_boolean` boolean column by sending a `PUT` request to `/EntityDefinitions(LogicalName='sample_bankaccount')/Attributes(LogicalName='sample_boolean')`.
+1. Update the option labels for the `sample_boolean` boolean column using the [UpdateOptionValue action](xref:Microsoft.Dynamics.CRM.UpdateOptionValue).
+1. Attempt to retrieve a `sample_datetime` datetime column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Attempt to retrieve a `sample_decimal` decimal column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Attempt to retrieve a`sample_integer` integer column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Attempt to retrieve a `sample_memo` memo column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Attempt to retrieve a `sample_money` money column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Attempt to retrieve a `sample_choice` choice column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Add a new option to the `sample_choice` column using the [InsertOptionValue action](xref:Microsoft.Dynamics.CRM.InsertOptionValue).
+1. Change the order of the  options of the `sample_choice` column using the [OrderOption action](xref:Microsoft.Dynamics.CRM.OrderOption).
+1. Delete one of the options of the `sample_choice` column using the [DeleteOptionValue action](xref:Microsoft.Dynamics.CRM.DeleteOptionValue).
+1. Attempt to retrieve a  `sample_multiselectchoice` multi-select choice column for the `sample_BankAccount` table, and create it if it doesn't exist.
+1. Create a new Status option for the `sample_BankAccount` table using the [InsertStatusValue Action](xref:Microsoft.Dynamics.CRM.InsertStatusValue). 
+
+### Section 3: Create and use Global OptionSet
+
+Operations:
+
+1. Create a new global choice named `sample_colors` by sending a `POST` request to `/GlobalOptionSetDefinitions`.
+1. Retrieve the `sample_colors` global choice by sending a `GET` request to  `/GlobalOptionSetDefinitions(<id value>)`.
+1. Create a new `sample_colors` choice column for the `sample_BankAccount` table using the `sample_colors` global choice by sending a `POST` request to `/EntityDefinitions(LogicalName='sample_bankaccount')/Attributes` and associating it to the global choice.
+
+### Section 4: Create Customer Relationship
+
+Operations:
+
+1. Create a new `sample_customerid` customer column for the `sample_BankAccount` table using the [CreateCustomerRelationships Action](xref:Microsoft.Dynamics.CRM.CreateCustomerRelationships).
+1. Retrieve the `sample_customerid` customer column by sending a `GET` request to `/EntityDefinitions(LogicalName='sample_bankaccount')/Attributes(LogicalName='sample_customerid')`.
+1. Retrieve the relationships created for the customer column by sending `GET` requests to `/RelationshipDefinitions(<id>)/Microsoft.Dynamics.CRM.OneToManyRelationshipMetadata`.`.
+
+### Section 5: Create and retrieve a one-to-many relationship
+
+Operations:
+
+1. Verify that the `sample_BankAccount` table is eligible to be referenced in a 1:N relationship using the [CanBeReferenced function](xref:Microsoft.Dynamics.CRM.CanBeReferenced).
+1. Verify that the `contact` table is eligible to be reference other tables in a 1:N relationship using the [CanBeReferencing function](xref:Microsoft.Dynamics.CRM.CanBeReferencing).
+1. Identify what other tables can reference the `sample_BankAccount` table in a 1:N relationship using the [GetValidReferencingEntities function](xref:Microsoft.Dynamics.CRM.GetValidReferencingEntities).
+1. Create a 1:N relationship between `sample_BankAccount` and `contact` tables by sending a `POST` request to `/RelationshipDefinitions`.
+1. Retrieve the 1:N relationship by sending `GET` request to `/RelationshipDefinitions(<id>)/Microsoft.Dynamics.CRM.OneToManyRelationshipMetadata`.
+
+### Section 6: Create and retrieve a many-to-one relationship
+
+Operations:
+
+1. Create a N:1 relationship between `sample_BankAccount` and `account` tables by sending `POST` a request to `/RelationshipDefinitions`.
+1. Retrieve the N:1 relationship by sending a `GET` request to `/RelationshipDefinitions(<id>)/Microsoft.Dynamics.CRM.OneToManyRelationshipMetadata`.
+
+### Section 7: Create and retrieve a many-to-many relationship
+
+Operations:
+
+1. Verify that the `sample_BankAccount` and `contact` tables are eligible to participate in a N:N relationship using the [CanManyToMany function](xref:Microsoft.Dynamics.CRM.CanManyToMany).
+1. Verify that the `sample_BankAccount` and `contact` tables are eligible to participate in a N:N relationship using the [GetValidManyToMany Function](xref:Microsoft.Dynamics.CRM.GetValidManyToMany).
+1. Create a N:N relationship between `sample_BankAccount` and `contact` tables by sending a `POST` request to `/RelationshipDefinitions`.
+1. Retrieve the N:N relationship by sending `GET` request to `/RelationshipDefinitions(<id>)/Microsoft.Dynamics.CRM.ManyToManyRelationshipMetadata`.
+
+### Section 8: Export managed solution
+
+Operations: Export the solution created in [Section 0: Create Publisher and Solution](#section-0-create-publisher-and-solution) containing the items created in this sample using the [ExportSolution Action](xref:Microsoft.Dynamics.CRM.ExportSolution).
+
+### Section 9: Delete sample records
+
+Operations: A reference to each record created in this sample was added to a list as it was created. In this sample the records are deleted in the reverse order in which they were created.
+
+### Section 10: Import and Delete managed solution
+
+Operations:
+
+1. Import the solution exported in [Section 8](#section-8-export-managed-solution) using the [ImportSolution action](xref:Microsoft.Dynamics.CRM.ImportSolution).
+1. Query the solution table to get the `solutionid` of the imported solution.
+1. Delete the imported solution using the `solutionid`.
+
+## Clean up
+
+By default this sample will delete all the records created in it. If you want to view created records after the sample is completed, change the `deleteCreatedRecords` variable to `false` and you will be prompted to decide if you want to delete the records.
+
+### See also
+
+[Use the Dataverse Web API](../overview.md)<br />
+[Use the Web API with table definitions](../use-web-api-metadata.md)<br />
+[Web API Samples](../web-api-samples.md)<br />
+[Web API Basic Operations Sample (PowerShell)](basic-operations-powershell.md)
+
+[!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/webapi/samples/metadata-operations-powershell.md

@@ -49,6 +49,8 @@ items:
     href: ../web-api-samples-powershell.md
   - name: Basic Operations
     href: basic-operations-powershell.md
+  - name: Metadata Operations
+    href: metadata-operations-powershell.md
 - name: (JavaScript) samples
   items:
   - name: About the client-side samples

powerapps-docs/developer/data-platform/webapi/samples/toc.yml

@@ -1,7 +1,7 @@
 ---
 title: "Web API  Data operations Samples PowerShell"
 description: "This article provides a description of Web API samples that are implemented using PowerShell"
-ms.date: 01/20/2024
+ms.date: 05/14/2024
 author: divkamath
 ms.author: dikamath
 ms.reviewer: jdaly
@@ -25,7 +25,7 @@ The following samples use the patterns described here:
 |Not available yet| [Web API Query Data Sample](web-api-query-data-sample.md)| Demonstrates how to use OData v4 query syntax and functions and Dataverse query functions. Includes examples of working with predefined queries and using FetchXML to perform queries. |
 |Not available yet| [Web API Conditional Operations Sample](web-api-conditional-operations-sample.md) | Demonstrates how to perform conditional operations you specify with ETag criteria.|
 |Not available yet|[Web API Functions and Actions Sample](web-api-functions-actions-sample.md)| Demonstrates how to use bound and unbound functions and actions, including custom actions.|
-|Not available yet|[Web API table schema operations sample](web-api-metadata-operations-sample.md)|Demonstrates how to perform selected operations that modify the Dataverse schema, or metadata.|
+|[Web API table schema operations sample (PowerShell)](samples/metadata-operations-powershell.md)|[Web API table schema operations sample](web-api-metadata-operations-sample.md)|Demonstrates how to perform selected operations that modify the Dataverse schema, or metadata.|
 
 
 ## Prerequisites

powerapps-docs/developer/data-platform/webapi/web-api-samples-powershell.md

@@ -3,7 +3,7 @@ title: "getEventSource (Client API reference) in model-driven apps| MicrosoftDoc
 description: "Learn about the getEventSource method that returns a reference to the object that the event occurred on." 
 author: adrianorth
 ms.author: aorth
-ms.date: 03/12/2022
+ms.date: 05/15/2024
 ms.reviewer: jdaly
 ms.topic: reference
 applies_to: "Dynamics 365 (online)"
@@ -24,7 +24,7 @@ Returns a reference to the object that the event occurred on.
 
 **Type**: Object
 
-**Description**: Returns the object from the **Xrm** object model that is the source of the event, not an HTML DOM object. For example, in an [OnChange](../events/attribute-onchange.md) event, this method returns the **formContext.data.entity**  object that represents the changed column.
+**Description**: Returns the object from the **Xrm** object model that is the source of the event, not an HTML DOM object. For example, in an [OnChange](../events/attribute-onchange.md) event, this method returns an item from the **formContext.data.entity.attributes**  collection that represents the changed column.
 
 [!INCLUDE[cc-terminology](../../../../data-platform/includes/cc-terminology.md)]
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/executioncontext/getEventSource.md

@@ -3,7 +3,7 @@ title: Power Apps Test Engine overview (preview)
 description: Learn about how you can automate tests of standalone canvas apps using the Power Apps Test Engine within Power Platform CLI.
 author: pvillads
 ms.author: pvillads
-ms.date: 08/16/2023
+ms.date: 05/14/2024
 ms.reviewer: jdaly
 ms.topic: article
 contributors:
@@ -159,7 +159,8 @@ If you move an app that is _not_ part of a solution to a new environment, you'll
 
 ### See also
 
+[Power Apps Test Engine release notes](https://github.com/microsoft/PowerApps-TestEngine/releases)   
 [Power Apps Test Engine YAML format (preview)](yaml.md)   
-[Power Apps Test Engine Power Fx functions (preview)](powerfx.md)   
+[Power Apps Test Engine Power Fx functions (preview)](powerfx.md)
 
 [!INCLUDE [footer-banner](../../includes/footer-banner.md)]

powerapps-docs/developer/test-engine/overview.md

@@ -245,6 +245,8 @@
     href: search.md
   - name: Get help from a virtual agent
     href: ./common/virtual-agent.md
+  - name: Copilot in Power Apps overview
+    href: ./canvas-apps/ai-overview.md
 - name: Canvas apps
   items:
   - name: Canvas apps
@@ -286,10 +288,8 @@
           - name: Troubleshoot common errors
             href: ./canvas-apps/figma/common-errors.md
             displayName: Troubleshoot common errors when creating app from Figma
-    - name: Create an app using AI Copilot 
+    - name: Create an app using Copilot
       items:
-      - name: Overview
-        href: ./canvas-apps/ai-overview.md
       - name: Create an app from conversations
         href: ./canvas-apps/ai-conversations-create-app.md
       - name: Continue editing your app with Copilot (preview)
@@ -2041,8 +2041,10 @@
           href: ./data-platform/lowcode-plug-ins-examples.md
         - name: Low-code plug-ins Power Fx
           href: ./data-platform/low-code-plug-ins-powerfx.md
-        - name: Create low-code plug-ins to use with a copilot (preview)
+        - name: Create low-code plug-ins to use with a copilot
           href: ./data-platform/low-code-plugins-copilot-studio.md
+        - name: Low-code plug-ins tips and known issues
+          href: ./data-platform/low-code-plug-ins-tips.md
       - name: Work with actions
         items:
         - name: Use actions
@@ -2199,6 +2201,12 @@
     href: ./model-driven-apps/privileges-required-customization.md
   - name: API limits overview
     href: ./data-platform/api-limits-overview.md
+  - name: Get experimental features early (preview)
+    items:
+    - name: Use the Dataverse accelerator
+      href: ./data-platform/dataverse-accelerator/dataverse-accelerator.md
+    - name: Monitor plug-ins
+      href: ./data-platform/dataverse-accelerator/plugin-monitoring.md
   - name: For admins
     items:
     - name: Security in Dataverse