Pull from main

Author: Mattp123

powerapps-docs/developer/data-platform/fetchxml/optimize-performance.md

@@ -27,7 +27,7 @@ If you select many lookup and computed columns, and you're experiencing performa
 Using the `latematerialize` attribute might not always provide a performance benefit. It might make simple queries run more slowly. It's most beneficial when your query:
 
 - Has many joins
-- Contains many columns lookup columns or computed columns
+- Contains many lookup or computed columns
 
 ## Query Hints
 

powerapps-docs/maker/TOC.yml

@@ -686,6 +686,8 @@
           href: ./canvas-apps/set-aspect-ratio-portrait-landscape.md
         - name: Create responsive layout
           href: ./canvas-apps/create-responsive-layout.md
+        - name: Understand app functionality through code view (preview) 
+          href: ./canvas-apps/code-view.md
       - name: Configure app functionality
         items:
         - name: Get started with formulas

powerapps-docs/maker/canvas-apps/code-view.md

@@ -0,0 +1,75 @@
+---
+title: Understand your app's functionality through code view (preview)
+description: Understanding app functionality through code view for canvas apps.
+author: marcelbf
+
+ms.custom: canvas
+ms.collection: get-started
+ms.topic: conceptual
+ms.reviewer: mkaur
+ms.date: 5/14/2024
+ms.subservice: canvas-maker
+ms.author: marcelbf
+search.audienceType: 
+  - maker
+  - developer
+---
+# Understand app functionality through code view (preview)
+
+[This article is prerelease documentation and is subject to change.]
+
+Use code view to see your app's underlying code to better understand the app's functionality. Each control on the screen has a code representation that uses a format that is a subset of YAML and an improvement from the [YAML formula grammar](/power-platform/power-fx/yaml-formula-grammar).
+
+With code view you can:
+
+- See a code representation of each control on your screen.
+- Copy a control as code and share outside of Power Apps Studio.
+- Copy an paste a control as code and create new control based on the copied code.
+
+> [!IMPORTANT]
+> - Format is subjected to change. We don’t guarantee compatibility with the final version.
+> - The current code format isn't suitable to source control during the preview period.
+
+## Prerequisites 
+
+ The Power Fx formula bar must be turned on to view the code for a control.
+
+The formula bar is **ON** by default for new apps. For existing apps, follow these steps to turn on the Power Fx formula bar:
+ - Open our app in Power Apps Studio, select **Settings** > **Upcoming features** > **Preview** > set the **Power Fx formula bar** toggle to **ON**.
+
+
+## View, copy, and paste code
+
+The **View code** feature shows the code for the selected control and all underlying controls. You can also use the shortcut **Ctrl + F** to find a specific string in the code.
+
+Follow these steps to view, copy, and paste the code for a control:
+
+1. Open your app for [editing](edit-app.md) in Power Apps Studio.
+1. **Right-click** on the control in the **Tree view** or on the screen or and then select, **View code (preview)**. 
+
+    :::image type="content" source="media/code-view/view-code.png" alt-text="View code for a control":::
+
+1. Select **Copy code** and then paste the copied code into any window outside of your browser.
+
+1. To generate a new control from the copied code, right-click on the control where you want to create a new control and the select, **Paste code (preview)**. 
+
+    :::image type="content" source="media/code-view/paste-code.png" alt-text="Paste code ":::
+
+
+     You must use the YAML format that's generated by Power Apps Studio. The code also goes through validation check before it's created.
+
+## Know limitations
+
+* You can't copy and paste and there’s no code view for the **App Object**.
+* You can’t edit the code in the code view.
+* You can only copy controls that are on a screen. Copying a screen isn't supported.
+
+This article provides an overview of working with formulas. For more detailed information about functions, operators, and other building blocks, see [Formula reference](formula-reference.md).
+
+### See also
+
+[YAML format](/power-platform/power-fx/yaml-formula-grammar)
+[Formula bar](formula-bar-find-replace.md)
+[Use Find and Replace capability in the formula bar](formula-bar-find-replace.md)
+
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/canvas-apps/media/code-view/paste-code.png

@@ -4,7 +4,7 @@ metadata:
   description: Get answers to frequently asked questions about long term retention with Dataverse.
   author: Mattp123
   ms.search.keywords: 
-  ms.date: 05/13/2024
+  ms.date: 05/29/2024
   ms.author: matp
   ms.reviewer: 
   contributors: gned
@@ -31,7 +31,7 @@ sections:
      answer: |
         Yes. Errors from a policy run are available in the run history details. More information: data-retention-manage.md#view-and-manage-retention-policies
 
-   - question: What if a maker adds custom columns or deletes columns to tables that have existing retained data in Dataverse long term retention?
+   - question: Will Dataverse schema changes be handled by Dataverse long term retention? What if a maker adds custom columns or deletes columns to tables that have existing retained data in Dataverse long term retention?
      answer: |
         The changes are reflected in the long term retained data. When retention policies run, the new custom columns contain data for the new rows. The data that was retained prior to these changes won't have any value in these columns. If a column is deleted in the live table, the column remains in the long term retained data with a value for all new rows.