Live publish for 02 August 2024.

Author: bishalgoswami

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

@@ -6,7 +6,7 @@ author: pnghub
 ms.author: gned
 ms.reviewer: matp
 ms.topic: overview
-ms.date: 05/10/2024
+ms.date: 08/02/2024
 ms.custom: template-overview
 ---
 # Dataverse long term data retention overview
@@ -46,7 +46,7 @@ Application admins set up custom policies for a table with criterion to retain d
 
 > [!IMPORTANT]
 > - Once data is retained with Dataverse long term retention it can't be moved back to the Dataverse live (active) application state.
-> - Customers using self-managed encryption key (BYOK) should be aware that long term retained data in the Azure data lake is encrypted with Microsoft managed key. Consider migrating to customer managed key. More information: [Migrate bring-your-own-key environments to customer-managed key](/power-platform/admin/cmk-migrate-from-byok)
+> - You can't use the long term data retention feature with environments that have either self-managed encryption key [bring your own key](/power-platform/admin/cmk-migrate-from-byok) or [customer managed key](/power-platform/admin/cmk-migrate-from-byok) enabled.
 > - When a retention policy is run, the process makes API requests in Microsoft Power Platform. These requests are counted towards the existing API requests available with your plan. More information: [Requests limits and allocations](/power-platform/admin/api-request-limits-allocations)
 
 Dataverse provides read-only access to the retained data via:

powerapps-docs/maker/data-platform/define-query-hierarchical-data.md

@@ -2,9 +2,8 @@
 title: "Define and query hierarchical data with Microsoft Dataverse | MicrosoftDocs"
 description: "Learn how to define and query hierarchically related data"
 ms.custom: ""
-ms.date: 06/02/2018
+ms.date: 08/02/2024
 ms.reviewer: ""
-
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "conceptual"
@@ -22,9 +21,10 @@ search.audienceType:
 ---
 # Define and query hierarchically related data
 
+> [!IMPORTANT]
+> This feature is deprecated. For more information, go to [Hierarchy control in model-driven apps is deprecated](/power-platform/important-changes-coming#hierarchy-control-in-model-driven-apps-is-deprecated).
 
-
-You can get valuable business insights by defining and querying hierarchically related data. The hierarchical modelling and visualization capabilities give you a number of benefits:  
+You can get valuable business insights by defining and querying hierarchically related data. The hierarchical modeling and visualization capabilities give you a number of benefits:  
 
 - View and explore complex hierarchical information.  
 - View key performance indicators (KPIs) in the contextual view of a hierarchy.  
@@ -45,7 +45,7 @@ When a self-referential one-to-many (1:N) relationship exists, in the relationsh
 
 To query the data as a hierarchy, you must set one of the table’s one-to-many (1:N) self-referential relationships as hierarchical. 
 
-To turn the hierarchy on:  
+To turn on the hierarchy:  
 
 1. While [viewing 1:N relationships](create-edit-1n-relationships-solution-explorer.md#view-table-relationships), select the self-referential relationship  you want to edit.
 2. In the relationship definition, set **Hierarchical** to **Yes**.  
@@ -66,7 +66,7 @@ To turn the hierarchy on:
 
 ## Query hierarchical data  
 
-Without a defined hierarchy, to retrieve hierarchical data, need to iteratively query for the related rows. With a defined hierarchy, you can query the related data as a hierarchy in one step. You are able to query rows using the **Under** and **Not Under** logic. The **Under** and **Not Under** hierarchical operators are exposed in Advanced Find and the workflow editor. For more information about how to use these operators, see [Configure workflow steps](/flow/configure-workflow-steps#setting-conditions-for-workflow-actions). For more information about Advanced Find, see [Create, edit, or save an Advanced Find search](/dynamics365/customer-engagement/basics/save-advanced-find-search)  
+Without a defined hierarchy, to retrieve hierarchical data, need to iteratively query for the related rows. With a defined hierarchy, you can query the related data as a hierarchy in one step. You're able to query rows using the **Under** and **Not Under** logic. The **Under** and **Not Under** hierarchical operators are exposed in Advanced Find and the workflow editor. For more information about how to use these operators, see [Configure workflow steps](/flow/configure-workflow-steps#setting-conditions-for-workflow-actions). For more information about Advanced Find, see [Create, edit, or save an Advanced Find search](/dynamics365/customer-engagement/basics/save-advanced-find-search)  
 
 > [!NOTE]
 > Developers will also be able to use these operators in code. More information [Developer Documentation: Query hierarchical data](/dynamics365/customer-engagement/developer/org-service/query-hierarchical-data)

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

@@ -5,7 +5,7 @@ author: sanjeevgoyalmsft
 reviewer: mattp123
 ms.topic: how-to
 ms.custom: 
-ms.date: 06/28/2024
+ms.date: 08/01/2024
 ms.subservice: teams
 ms.author: dikamath
 ms.reviewer: matp
@@ -159,8 +159,8 @@ You can use the following function types in a formula column:
 
 ## Functions
 
-You can use the following scalar functions in a formula column:
-
+For the scalar functions you can use in a formula column, go to [Formula reference - Dataverse formula columns](/power-platform/power-fx/formula-reference-formula-columns).
+<!--
 :::row:::
    :::column span="":::
       [Abs](../canvas-apps/functions/function-numericals.md)
@@ -357,7 +357,7 @@ You can use the following scalar functions in a formula column:
    :::column-end:::
    :::column span="":::
    :::column-end:::
-:::row-end:::
+:::row-end::: -->
 
 \* The **Text** and **Value** functions only work with whole numbers, where no decimal separator is involved. The decimal separator varies across locales. Since formula columns are evaluated without locale knowledge, there's no way to properly interpret or generate the decimal separator.
 

powerapps-docs/maker/data-platform/low-code-plug-ins-powerfx.md

@@ -5,7 +5,7 @@ author: Mattp123
 ms.author: matp
 ms.service: powerapps
 ms.topic: how-to
-ms.date: 04/09/2024
+ms.date: 08/02/2024
 ms.custom: template-how-to
 ---
 # Low-code plug-ins Power Fx (preview)
@@ -32,7 +32,11 @@ The following table lists the Power Fx formulas that work but have limitations o
 |Collect     | Yes        | Requires the variable to exist and the variable type to match what you’re trying to set it to.    |
 |Defaults     |  No       | Use Collect instead. For example, instead of *Patch(account, Defaults(account), {“Account Name”: “Example Account”})* use `Collect(account, {“Account Name”: “Example Account”})`.    |
 
-## Formulas not currently supported with low-code plug-ins
+## Power Fx formulas supported
+
+For information about the formulas supported with low-code plug-ins, go to [Formula reference- Dataverse plug-ins](/power-platform/power-fx/formula-reference-plug-ins).
+
+Formulas *not currently supported* with low-code plug-ins
 
 :::row:::
    :::column span="":::

powerapps-docs/maker/data-platform/visualize-hierarchical-data.md

@@ -2,9 +2,8 @@
 title: "Configure visualizations for hierarchical data with model-driven apps | MicrosoftDocs"
 description: "Learn how to query and visualize hierarchical related data"
 ms.custom: ""
-ms.date: 06/11/2020
+ms.date: 08/02/2024
 ms.reviewer: ""
-
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "article"
@@ -20,7 +19,8 @@ search.audienceType:
 ---
 # Visualize hierarchical data with model-driven apps
 
-
+> [!IMPORTANT]
+> This feature is deprecated. For more information, go to [Hierarchy control in model-driven apps is deprecated](/power-platform/important-changes-coming#hierarchy-control-in-model-driven-apps-is-deprecated).
 
 When a table is configured to have a hierarchical self-referential relationship you can configure visualizations using that hierarchy. More information: [Define and query hierarchically related data](../data-platform/define-query-hierarchical-data.md)
 
@@ -37,20 +37,20 @@ The  tables that have visualizations available by default include [Account](/pow
 
 ## Important things to remember 
 
-- Only one (1:N) self-referential relationship per table can be set as hierarchical. In a self-referential relationship the primary table and the related table must be of the same type.  
+- Only one (1:N) self-referential relationship per table can be set as hierarchical. In a self-referential relationship, the primary table and the related table must be of the same type.  
 - A hierarchy or visualization is based on one table only. You can depict the account hierarchy showing accounts at multiple levels, but you can’t show accounts and contacts in the same hierarchy visualization. 
-- The maximum number of columns that can be displayed in a tile is three with Unified Interface and four with the legacy web client. If you add more columns to the Quick Form that is used for the tile view, only the first three columns will be displayed. 
+- The maximum number of columns that can be displayed in a tile is three with Unified Interface and four with the legacy web client. If you add more columns to the Quick Form that is used for the tile view, only the first three columns are displayed. 
 
 ## Hierarchy settings
 
-To enable visualizations for a hierarchy you must connect the hierarchy to a quick view form. This can only be done using solution explorer.
+To enable visualizations for a hierarchy, you must connect the hierarchy to a quick view form. This can only be done using solution explorer.
 
 [!INCLUDE [cc_navigate-solution-from-powerapps-portal](../../includes/cc_navigate-solution-from-powerapps-portal.md)]
 
 The hierarchy settings are associated to a table in the solution explorer. 
 
 1. While [viewing tables](../data-platform/create-edit-entities-solution-explorer.md#view-tables), select **Hierarchy Settings**.
-2. If an existing hierarchy setting exists you can edit it. Otherwise click **New** to create a new one.
+2. If an existing hierarchy setting exists, you can edit it. Otherwise select **New** to create a new one.
 
     > [!NOTE]
     > If the hierarchy settings do not exist the table is not eligible to have a hierarchy configured.
@@ -60,15 +60,15 @@ The hierarchy settings are associated to a table in the solution explorer.
 
 |Column|Description|
 |--|--|
-|**Name**|*Required.* Add a unique name for the hierarchy settings. This is typically just the name of the table. This value will include the solution publisher's customization prefix.|
+|**Name**|*Required.* Add a unique name for the hierarchy settings. This is typically just the name of the table. This value includes the solution publisher's customization prefix.|
 |**Default Quick View Form**|*Required.* Choose from an existing Quick View form or choose **Create New** to open the Quick View form editor to create a new one.|
-|**Hierarchical Relationship**|*Required.* If a hierarchical relationship is already defined for the table the value will be set here. If there is no value, select **Mark a relationship as enabled for hierarchies** to open a dialog to choose one of the available self-referential relationships.|
+|**Hierarchical Relationship**|*Required.* If a hierarchical relationship is already defined for the table the value will be set here. If there's no value, select **Mark a relationship as enabled for hierarchies** to open a dialog to choose one of the available self-referential relationships.|
 |**Description**|Include a description of the purpose for this hierarchy so that future people customizing the system can understand why this was done.|
 
 
 The same hierarchical settings for visualization are set once, but apply to both web and mobile clients. In tablets, the visuals render in a modified format suitable for the smaller form factor. The customizable components required for hierarchical visualization are solution aware, therefore, they can be transported between organizations like any other customization. You can configure the attributes shown in the visualization by customizing a Quick Form using the form editor.
 
-## Visualization walk through
+## Visualization walk-through
 
 Let’s look at an example of creating the visualization for a custom table. We created a custom table called `new_Widget`, created a (1:N) self-referential relationship `new_new_widget_new_widget` and marked it as hierarchical, as shown here.  
 
@@ -87,7 +87,7 @@ For the **Quick View Form**, we created a Quick Form called **Widget Hierarchy T
 > [!div class="mx-imgBorder"] 
 > ![Create quick form for widget.](media/create-quickform.png)  
   
-After we completed the setup, we created two rows: *Standard Widget* and *Premium Widget*. After making the Premium Widget a parent of the Standard Widget by using the lookup column, the `new_Widget` grid view depicted the hierarchy icons, as shown below:  
+After we completed the setup, we created two rows: *Standard Widget* and *Premium Widget*. After making the Premium Widget a parent of the Standard Widget by using the lookup column, the `new_Widget` grid view depicted the hierarchy icons, as shown here:  
 
 > [!div class="mx-imgBorder"] 
 > ![Widget's hierarchy grid.](media/widget-hierarchy-grid.png)  

powerapps-docs/maker/model-driven-apps/commanding-use-powerfx.md

@@ -198,9 +198,13 @@ Self.Selected.Item.'Recurring Appointments'
 Self.Selected.Item.'Parent Account'.'Account Name'="parent"
 ```
 
-## Functions not supported
+## Functions available with commanding
 
-The following Power Fx functions are currently not supported with commanding in model-driven apps.
+For information about the formulas supported with commanding in model-driven apps, go to [Formula reference - model-driven apps](/power-platform/power-fx/formula-reference-model-driven-apps).
+
+### Functions not supported
+
+The following Power Fx functions are *currently not supported* with commanding in model-driven apps.
 
 - Back()
 - Clear()