Merge pull request #8359 from MicrosoftDocs/main

Sally - latest from Main

Author: sericks007

powerapps-docs/developer/data-platform/org-service/samples/azure-aware-custom-plugin.md

@@ -1,7 +1,7 @@
 ---
 title: "Azure aware custom plug-in (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This sample plug-in can post the pipeline execution context to the Azure Service Bus." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 04/03/2022
+ms.date: 06/19/2023
 author: jaredha
 ms.author: jaredha
 ms.reviewer: jdaly
@@ -20,10 +20,18 @@ The plug-in demonstrates how to obtain the execution context and the tracing ser
 ## How to run this sample
 
 1. Download or clone the [Samples](https://github.com/Microsoft/PowerApps-Samples) repo so that you have a local copy.
-2. Open the sample solution in Visual Studio and sign the assembly with a key.
-3. Register the plug-in using the **Plugin Registration Tool**.
+1. Open the `Azureplugin.sln` solution file located at `PowerApps-Samples\dataverse\orgsvc\C#\Azureplugin` with Visual Studio.
+1. Sign the assembly with a key.
+1. Register the plug-in using the **Plugin Registration Tool**.
 
 > [!NOTE]
 > This sample requires a service endpoint to be created first, and its ID passed to the plug-in constructor through the unsecure configuration parameter when the plug-in step is registered.
 
+More information:
+
+[Write a custom Azure-aware plug-in](../../write-custom-azure-aware-plugin.md)  
+[Register a plug-in](../../register-plug-in.md)
+
+
+
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/write-custom-azure-aware-plugin.md

@@ -1,7 +1,7 @@
 ---
 title: "Write a custom Azure-aware plug-in (Microsoft Dataverse) | Microsoft Docs"
 description: "Learn how to write plug-in code that can post a message or the execution context of the current database transaction to the Azure Service Bus."
-ms.date: 04/03/2022
+ms.date: 06/19/2023
 author: divkamath
 ms.author: dikamath
 ms.reviewer: pehecke
@@ -132,10 +132,11 @@ For a plug-in registered to execute asynchronously, the <xref:Microsoft.Xrm.Sdk.
 
 ### See also
 
-[Azure extensions for Dynamics 365](azure-integration.md)<br />
-[Send Dynamics 365 data over the Microsoft Azure Service Bus](work-data-azure-solution.md)<br />
-[Write a plug-In](write-plug-in.md)<br />
-[Event execution pipeline](event-framework.md)<br />
+[Azure extensions for Dynamics 365](azure-integration.md)  
+[Send Dynamics 365 data over the Microsoft Azure Service Bus](work-data-azure-solution.md)  
+[Sample: Azure aware custom plug-in](org-service/samples/azure-aware-custom-plugin.md)  
+[Write a plug-In](write-plug-in.md)  
+[Event execution pipeline](event-framework.md)  
 [Register and deploy plug-Ins](register-plug-in.md)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/TOC.yml

@@ -2425,6 +2425,8 @@
           href: ../cards/make-a-card/ui-elements/use-buttons.md
         - name: Add and configure screens
           href: ../cards/make-a-card/screens/use-screens.md
+        - name: Work with repeating controls in cards
+          href: ../cards/make-a-card/ui-elements/data-binding.md
         - name: Control reference
           items: 
             - name: List of controls and properties

powerapps-docs/maker/data-platform/data-retention-set.md

@@ -5,7 +5,7 @@ author: Mattp123
 ms.author: matp
 ms.service: powerapps
 ms.topic: how-to 
-ms.date: 05/09/2023
+ms.date: 06/19/2023
 ms.custom: template-how-to
 ---
 # Set a data retention policy for a table (preview)
@@ -79,6 +79,8 @@ Power Platform administrators setup retention policies.
 Now you can view and manage the policy. More information: [Manage data retention policies](data-retention-manage.md)
 
 > [!IMPORTANT]
+>
+> - The retention policy can't be set for the tables where bulk delete isn't supported. For example, Activity Pointer, Activity Party, and Attachment tables don't support bulk delete.
 > - The parent table and all related rows from child tables, of the parent, will be marked and stored in Dataverse long term storage.
 > - Logic associated with an existing delete action of any table (parent and children) will always be executed during the policy run.
 > - A policy run will take from 72-96 hours irrespective of the data volume. Data retention policies are given a low priority by the platform. Dataverse will always run the retention process in the background to avoid any impact on other platform services, such as apps and flows.
@@ -91,4 +93,5 @@ If a parent table has many child tables, and the size of the parent or child tab
 ## Next steps
 
 [Manage data retention policies](data-retention-manage.md) <br />
-[Share your ideas](https://experience.dynamics.com/ideas/categories/list/?category=55f731de-11f3-ed11-8848-00224827ed7b&forum=eef9aef6-0ff3-ed11-8848-00224827e88b)
+[Share your ideas](https://experience.dynamics.com/ideas/categories/list/?category=55f731de-11f3-ed11-8848-00224827ed7b&forum=eef9aef6-0ff3-ed11-8848-00224827e88b) <br />
+[For developers: Long-term data retention](../../developer/data-platform/long-term-retention.md)

powerapps-docs/maker/model-driven-apps/form-component-control.md

@@ -127,7 +127,7 @@ Note the following limitations when you add the form component control to a tabl
 
 - The form that you use with a form component must be included in your app. If it isn't, or if the current user doesn't have access to the form, it will fall back to the top-most main form that is included in the app and available to the user (based on form order). More information: [Add a component](add-edit-app-components.md#add-a-component).
 
-- Form component controls have certain limitations when rendered in multi-session apps. If the client API is used to modify the form component control, the changes might not be persisted when switching multi-session tabs.
+- Form component controls have certain limitations when rendered in multi-session apps. If the client API is used to modify the form component control, or if data is entered on the form, the changes might not be persisted when switching multi-session tabs.
 
 - You may notice that the timeline wall may not update when a column that is used to set the timeline wall has changed in the form component. When the page is refreshed the timeline wall will update as expected.