Merge branch 'main' into jdaly-main-work-with-data

Author: JimDaly

powerapps-docs/developer/model-driven-apps/clientapi/reference/executioncontext/getEventSource.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/maker/TOC.yml

@@ -53,6 +53,8 @@
     href: ../user/app-source.md
   - name: Draft well-written, input text with Copilot (preview)
     href: ../user/well-written-input-text-copilot.md
+  - name: Filter, sort, and search galleries with Copilot (preview)
+    href: ../user/smartGrid.md
   - name: 'Use model-driven apps'
     items:
     - name: Overview

powerapps-docs/maker/common/wrap/create-key-vault-for-code-signing.md

@@ -82,11 +82,11 @@ In this article, you will learn how to use an existing Azure Key Vault or create
          > [!NOTE]
          > When you upload to the Key Vault, you'll need to provide the password that you set in previous step for the .p12 file.
         
-       3. [Create the provisioning profile](code-sign-ios.md#create-an-ios-provisioning-profile) and run this command to encode it to base64:
-          - Mac: base64 `-i example.mobileprovision`
+       4. [Create the provisioning profile](code-sign-ios.md#create-an-ios-provisioning-profile) and run this command to encode it to base64:
+          - Mac: `base64 -i example.mobileprovision`
           - Windows:  `certutil -encode data.txt tmp.b64`
 
-       4. Upload the `base64` string obtained from the previous step to the Key Vault secret. Next, upload the .pfx file to Key Vault Certificate.
+       5. Upload the `base64` string obtained from the previous step to the Key Vault secret. Next, upload the .pfx file to Key Vault Certificate.
 
 
           :::image type="content" source="media/wrap-canvas-app/wrap-2.png" alt-text="Create a cert for iOS.":::

powerapps-docs/maker/data-platform/data-platform-import-export.md

@@ -95,28 +95,28 @@ Sometimes, a primary key might not work when you integrate data from an external
 Example:  
 For an **Account** table, you might set **transactioncurrencyid** as an alternate key by using a natural key-based identification. For example, use **US Dollar** instead of the GUID value **88c6c893-5b45-e811-a953-000d3a33bcb9** shown previously. You can also choose **currency symbol** or **currency name** as keys.  More information: [Define alternate keys using Power Apps portal](define-alternate-keys-portal.md)
 
-> [!div class="mx-imgBorder"] 
+> [!div class="mx-imgBorder"]
 > ![Example of creating an alternate key on a **Currency** table.](./media/data-platform-import-export/create-ak.png)
 
-> [!div class="mx-imgBorder"] 
+> [!div class="mx-imgBorder"]
 > ![Sample export file from an **Account** table showing **currency name** as a natural key.](./media/data-platform-import-export/export-nk.png)
 
 You can still use primary keys as identifiers after you specify alternate keys. In the preceding sample, the first file is still valid if GUIDs are valid data.
 
 ## Export data
 
-Export data from one or more tables. Exported data is in comma-separated value (CSV) format. When you export data from more than one table, each table is exported into its own CSV file.
+Export data from a single table in a comma-separated value (CSV) format.
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), on the left navigation pane select **Tables**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
 1. Select **Export** > **Export data**.
-1. Select the tables that you want to export data from, and then select **Export data**.
+1. Select the table from which you want to export data, and then select **Export data**.
 
-   > [!div class="mx-imgBorder"] 
+   > [!div class="mx-imgBorder"]
    > ![Example of exporting data from an **Account** table.](./media/data-platform-import-export/export-account.png)
 
 1. After the export finishes successfully, select **Download exported data** to download the CSV file to the download folder specified in your web browser.
 
-   > [!div class="mx-imgBorder"] 
+   > [!div class="mx-imgBorder"]
    > ![Sample export that shows successful export with link downloadable file.](./media/data-platform-import-export/export-success.png)
 
 > [!NOTE]
@@ -157,4 +157,8 @@ To fix this issue:
 
 After the fix completes, retry the export.
 
+## Permissions
+
+To import or export data, the user must have the **Environment Maker** security role.
+
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]