Pull from main

Author: Mattp123

powerapps-docs/maker/canvas-apps/connections/connection-excel.md

@@ -5,7 +5,7 @@ author: lancedMicrosoft
 
 ms.topic: reference
 ms.custom: canvas
-ms.date: 01/27/2022
+ms.date: 04/30/2024
 ms.subservice: canvas-maker
 ms.author: lanced
 ms.reviewer: mkaur
@@ -25,7 +25,7 @@ Ensure that the Excel data you want to use in Power Apps is [formatted as a tabl
 
 ## Step 2 - Store your Excel file in a cloud ___location
 
-Store the Excel file in a cloud-storage account, such as Dropbox, Google Drive, OneDrive, and OneDrive for Business. There are two versions of the Excel connector. The newer version of the connector can access more cloud locations.
+Store the Excel file in a cloud-storage account, such as Dropbox, Google Drive, OneDrive, and OneDrive for Business. There are two versions of the Excel connector. The newer version *[Excel Online (Business)](/connectors/excelonlinebusiness/)* of the connector can access more cloud locations.
 
 ## Step 3 - Add Excel as a data source for your Power App
 
@@ -39,6 +39,8 @@ Store the Excel file in a cloud-storage account, such as Dropbox, Google Drive,
 1. Enter the file ___location and select the table.
 1. When you're done, select **Create app**.
 
+## Use the Excel Online (Business) Connector
+In the past, Power Apps used the OneDrive connector to connect and get data from Excel. The OneDrive connector provided access to files on OneDrive and to Excel. Now authors should use the new recommended *[Excel Online (Business)](/connectors/excelonlinebusiness/)* connector. The Excel Online connector allows multiple users to access it and improved functionality.
 
 ## Other connectors
 

powerapps-docs/maker/data-platform/azure-synapse-link-build-apps-with-fabric.md

@@ -6,7 +6,7 @@ ms.author: Milindav
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to
-ms.date: 04/09/2024
+ms.date: 04/30/2024
 ms.custom: template-how-to
 ---
 # Build apps and automations, drive action with insights from Microsoft Fabric (preview)
@@ -46,7 +46,7 @@ Follow these steps to create a virtual table using Fabric data.
 
 > [!NOTE]
 >
-> This feature is enabled by default with all environments. Admins can disable this feature in the Power Platform admin center in the environment feature settings.
+> This feature is enabled by default with all environments. Admins can disable this feature in the Power Platform admin center in the environment feature settings. 
 
 1. Sign into [Power Apps](https://make.powerapps.com), and then select **Tables** on the left navigation pane.
 2. On the command bar, select **New table** > **Create a virtual table**.
@@ -56,6 +56,11 @@ Follow these steps to create a virtual table using Fabric data.
 6. On the **Data** page, select a table from the list of tables shown from the lakehouse. Select **Configure table and column names that will be used in Dataverse** if you want to rename any of the fields or tables in Dataverse or to specify additional properties available for you in Dataverse. Select **Next**.
 7. If you selected the **Configure table and column names that will be used in Dataverse** checkbox, you're shown the table and column properties and you can modify them here. When you're done modifying them select **Next**.
 8. Verify that the field chosen for **primary key field** is a unique field. You might need to verify the default field selected by the system as the primary key.
+
+> [!NOTE]
+>
+> While the table you selected from Fabric Lakehouse might not have a primary key defined, you need to select a field that is unique to continue. If you don't select a unique field, the table might not show all the records. While the wizard selects a field based on metadata available, the selection might not be accurate.  
+
 9. Review the information shown, and then select **Finish**.
 
 A new Dataverse virtual table is created with data from Fabric.

powerapps-docs/maker/data-platform/azure-synapse-link-view-in-fabric.md

@@ -6,20 +6,17 @@ author: pnghub
 ms.author: gned
 ms.reviewer: matp
 ms.topic: overview
-ms.date: 04/11/2024
+ms.date: 05/01/2024
 ms.custom: template-overview
 ---
 # Dataverse long term data retention overview
 
 Microsoft Dataverse supports custom retention policies to securely retain unlimited data long term in a cost-efficient way. While Dataverse can support your business growth with no limit on active data, you might want to consider moving inactive data to the Dataverse long term retention store.
 
 > [!IMPORTANT]
-> You must meet *both* of the following two requirements to use all long term data retention features:
-> - The Power Platform environment must be a [Managed Environment](/power-platform/admin/managed-environment-overview). This also applies to Dynamics 365 customers who will be required to upgrade to a Managed Environment if the environment isn't already a Managed Environment.
+> The Power Platform environment where the retention policy resides must be a [Managed Environment](/power-platform/admin/managed-environment-overview). This also applies to Dynamics 365 customers who will be required to upgrade to a Managed Environment if the environment isn't already a Managed Environment.
 >
-> - A minimum of 1000 Dynamics 365 licenses or 1000 Power Apps per user licenses, or 1000 licenses from a combination of both in a single tenant.
->
-> Customers who don't meet these requirements can continue to create data retention policies, but the policies are disabled.
+> Customers who don't meet this requirement can continue to create data retention policies, but the policies are disabled.
 
 Watch this video to learn about Dataverse long term data retention.
 > [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RW15oAf]

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

@@ -1,7 +1,7 @@
 ---
 title: "Define rollup columns with Power Apps | MicrosoftDocs"
 description: "Learn how to define rollup columns."
-ms.date: 04/23/2024
+ms.date: 04/30/2024
 ms.topic: "conceptual"
 applies_to: 
   - "Dynamics 365 (online)"
@@ -178,7 +178,7 @@ You should be aware of certain conditions and restrictions when working with rol
 - A workflow wait condition can't use a rollup column.  
 - A rollup over the rollup column isn't supported.  
 - A rollup can't reference a calculated column that uses another calculated column, even if all the columns of the other calculated column are on the current table.
-- A rollup column doesn't update automatically if it uses a formula field that's dependent on time bound functions, such as `Now()`, `UTCNow()`, `IsUTCToday()`, or `UTCToday()`. The online recalculation option (a manual refresh on the form) or **Recalculate** button must be used to calculate the latest rollup column value.
+- A rollup column doesn't update automatically if it uses a formula column that's dependent on time bound functions `Now()` and `IsUTCToday()`. The online recalculation option (a manual refresh on the form) or **Recalculate** button must be used to calculate the latest rollup column value.
 - The rollup can only apply filters to the source table or related tables, simple columns or noncomplex calculated columns.  
 - A rollup can be done only over related tables with the 1:N relationship. A rollup can't be done over the N:N relationships.  
 - A rollup can't be done over the 1:N relationship for the Activity table or the Activity Party table.  

powerapps-docs/maker/data-platform/define-rollup-fields.md

@@ -5,7 +5,7 @@ author: sanjeevgoyalmsft
 reviewer: mattp123
 ms.topic: how-to
 ms.custom: 
-ms.date: 04/25/2024
+ms.date: 04/30/2024
 ms.subservice: teams
 ms.author: dikamath
 ms.reviewer: matp
@@ -395,6 +395,7 @@ This section describes guidelines and the known limitations with formula columns
 - A *simple formula column* is where the formula uses columns from the same record or uses hard coded values. For rollup columns, formula columns must be simple formula columns, such as this example rollup column.
    :::image type="content" source="media/formula-column-rollup1.png" alt-text="Example simple formula column for a rollup column":::
    :::image type="content" source="media/formula-column-rollup2.png" alt-text="Example rollup column configuration":::
+- A formula column which is dependent on time bound functions `UTCNow()` and `UTCToday()` can't be used in a rollup field.
 
 ### Power Fx text function recommendations
 

powerapps-docs/maker/data-platform/formula-columns.md

@@ -67,6 +67,11 @@ The custom page is a new page type within model-driven apps. Custom pages bring
 
 * When there are multiple custom pages in an app, the consent dialog asks for data permissions for all of the connectors in all the custom pages even if they haven't yet been opened.
 
+## Connections
+* All custom pages share the connection infrastructure, as if they were part of the same canvas app. For instance, if a model-driven app has two custom pages and one is connected to SQL Server while the other isn't, the consent dialog will still appear and require permission for SQL access even if the page being opened doesn't require it.
+* Custom pages in model-driven apps don't support connection detection through the *Connected.connected* property.
+
+
 ## See also
 
 [Model-driven app custom page overview](model-app-page-overview.md)

powerapps-docs/maker/model-driven-apps/model-app-page-issues.md

@@ -1,57 +1,34 @@
 ---
-title: Optimize for devices controls (preview)
+title: Optimize for devices (preview)
 description: Learn which controls and properties are supported for device-optimized screens.
 author: anuitz
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: sericks
-ms.date: 03/14/2024
+ms.date: 05/01/2024
 ms.subservice: canvas-maker
 ms.author: anuitz
 search.audienceType: 
   - maker
 contributors:
-  - sericks
-  - anuitz
+- gachasta 
+- sericks
 ms.contributors:
 - devangpandya
 ---
 
-# Optimize for devices controls (preview)
-
-[This article is prerelease documentation and is subject to change.]
-
-For a screen to be optimized for devices, it must use controls that are supported natively. You can filter the control **Insert** pane to only show device-optimized controls. 
+# Optimize for devices (preview)
 
+For a screen to be optimized for devices, it must use controls that are supported natively. You can filter the control Insert pane to only show device-optimized controls.
 :::image type="content" source="media/optimized-for-devices-control-filter.png" alt-text="The Insert pane is filtered to only show controls that are device-optimized.":::
 
 > [!Important]
-> - This is a preview feature.
+> - This is a preview feature. Documentation is subject to change.
 > - Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.
 
 ## Device-optimized controls
 
-The following controls are available for screens that are optimized for devices. All other controls are currently unsupported.
-
-### [Modern controls](../maker/canvas-apps/controls/modern-controls/modern-controls-reference.md)
-
-- Button
-- Check box
-- Date picker
-- Text
-- Text input
-- Toggle
-
-#### Turn on modern controls
-
-Makers must complete the following steps to turn on modern controls and themes for an app.
-
-1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
-1. In the navigation pane, select **Apps**.
-1. Select an app.
-1. Select **Settings** in the command bar.
-1. In the **Settings** window, select **General**.
-1. Turn on the **Modern controls and themes** option.
+The following controls are optimized for iOS and Android devices. All other controls are currently unsupported. A screen that has one or more unsupported controls automatically renders in a web view instead of native UI. Learn more: [Optimize for devices overview](optimize-for-devices-overview.md).
 
 ### [Controls](../maker/canvas-apps/reference-properties.md)
 
@@ -64,6 +41,7 @@ Makers must complete the following steps to turn on modern controls and themes f
 - Circle
 - Components
 - Container (horizontal and vertical included)
+- Form
 - Gallery (vertical, horizontal, flexible height)
 - Icon (all icons supported)
 - Image
@@ -73,34 +51,39 @@ Makers must complete the following steps to turn on modern controls and themes f
 - Text label
 - Timer
 
-## Unsupported controls
+### [Modern controls](../maker/canvas-apps/controls/modern-controls/modern-controls-reference.md)
+
+- Button
+- Check box
+- Date picker
+- Text
+- Text input
+- Toggle
+
+Learn more: [Overview of modern controls and themes in canvas apps](../maker/canvas-apps/controls/modern-controls/overview-modern-controls.md)
 
-If a screen is set for optimization for devices, but has an unsupported control, you see an error message in a box.
+## Unsupported controls
 
-:::image type="content" source="media/optimized-for-devices-control-error.png" alt-text="The error that shows when an unsupported control is on a screen set to optimize for devices.":::
+If a screen has an unsupported control, the screen automatically reverts to render with a web view.
 
 ## Device-optimized properties
 
-Some properties must be configured so they're optimized for devices. For example, consider the [barcode reader](../maker/canvas-apps/controls/control-barcodereader.md) control. The maker can select **Scan Inline** for the **Scanning mode** property. In Power Apps Studio, when this mode is selected, the control displays as a warning box indicating the control only works on mobile devices. On a device, in a screen optimized for devices, the control displays a camera feed to enable barcode scanning.
+Some properties must be configured so they're optimized for devices. For example, consider the [barcode reader](../maker/canvas-apps/controls/control-barcodereader.md) control. The maker can select **Scan Inline** for the **Scanning mode** property. In Power Apps Studio, when this mode is selected, the control displays as a warning box indicating that the control only works on mobile devices. On a device, in a screen optimized for devices, the control displays a camera feed to allow barcode scanning.
 
 ## Known limitations
 
 Note the following limitations with the 'optimize for devices' feature.
 
-- Only the **Segoe UI** font is supported. If a control is using another font, it displays the Segoe UI font instead. Due to the differences in fonts, the control can take up more or less space than expected. We recommend that you use the Segoe UI font for device-optimized screens.
-- The **Image** control, when showing an SVG, only supports the fit and stretch image position options. Its default behavior is to fit, if another option is selected. All other image types work as expected for all image positions.
-- In the **modern Text** control, the **Semi-bold** and **Medium** font weights aren't supported on Android devices. It displays a regular font weight instead.
+- The **Image** control, when showing an SVG file, only supports the fit, fill, and stretch image position options. Its default behavior is to fit, if another option is selected. All other image types work as expected for all image positions.
 - In the **modern Text input** control, the **Value** property, when set to a Power Fx variable, isn't displayed at first navigation. Instead, it shows the placeholder value until the user navigates away and back to the screen with the **modern Text input** control.
-- In the **modern Text input** control, the **OnChange** property is called twice when the control is exited, and then blurred.
+- In the **modern Text input** control, the **OnChange** property is called each time the user interacts with the control, instead of when navigating away from the control.
 - In the **modern Text input** control, the **Validate state** property doesn't display a red border around the control.
 - In the **Image** control, the **Image rotation** property isn't supported. The image isn't rotated.
 - In the **Dropdown** and **Radio** control, the **Items** property doesn't support references to other controls. Items aren't shown if they're complex values, like references.
 - In the **modern Date picker** control, tapping on the control opens a modal with a calendar instead of allowing users to type into the control directly.
 - In the **modern Date picker** control, the **Base palette color** and modern theme aren't applied on Android devices. Instead, it displays as the device's theme color.
 - In the **Button**, **Image**, **Label**, and **Icon** controls, the **SetFocus** Power Fx function doesn't support keyboard focus, only accessibility focus (for example, screen reader).
-- In **Horizontal and vertical containers**, the **Drop shadow** property isn't supported. Instead, containers display without drop shadow.
 - In **Horizontal and vertical containers**, the **Scroll** option only works for a single direction, depending on the **Wrap** property. If **Wrap** is off, the container is scrollable in the primary direction, otherwise it's scrollable in the secondary direction.
 - Multiple **Barcode reader** controls on a single screen aren't supported.
 - Multiple **Camera** controls on a single screen aren't supported.
 - In the **Camera** control, the **Display mode** property of the parent control isn't supported. For example, if the camera control is part of a form that is set to view mode, the camera might still be in edit mode.
-- On **Screen**, the **Background image** property isn't supported.