Merge pull request MicrosoftDocs#4462 from MicrosoftDocs/main638228197265659756sync_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

powerapps-docs/maker/TOC.yml

@@ -2423,6 +2423,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.