Merge branch 'main' into FetchXml

Author: JimDaly

powerapps-docs/developer/data-platform/TOC.yml

@@ -99,8 +99,8 @@
     - name: Bulk Operation messages
       href: bulk-operations.md
       items:
-      - name: Use DeleteMultiple (preview)
-        href: deletemultiple.md
+        - name: Use DeleteMultiple (preview)
+          href: deletemultiple.md
     - name: Create your own messages
       href: custom-actions.md
       items:
@@ -123,7 +123,7 @@
               href: org-service/samples/export-data-fetchxml-annotation-custom-api-sample.md
         - name: Use Custom Process Actions with code
           href: workflow-custom-actions.md
-    - name: Use open types with custom APIs 
+    - name: Use open types with custom APIs
       href: use-open-types.md
     - name: Background operations (preview)
       href: background-operations.md
@@ -381,7 +381,7 @@
           href: aaduser-entity.md
     - name: Template tables
       href: upload-manage-document-templates.md
-    - name: Long-term data retention (preview)
+    - name: Long-term data retention
       href: long-term-retention.md
 - name: Work with table definitions using code
   href: metadata-services.md
@@ -446,7 +446,7 @@
       href: customize-labels-support-multiple-languages.md
     - name: Best Practices
       href: best-practices/work-with-metadata/index.md
-- name: Work with elastic tables using code  
+- name: Work with elastic tables using code
   items:
     - name: Overview of elastic tables
       href: elastic-tables.md

powerapps-docs/developer/data-platform/dataverse-sql-query.md

@@ -2,7 +2,7 @@
 title: "Long-term data retention (Microsoft Dataverse) | Microsoft Docs"
 description: "Dataverse long-term data retention enables customers to retain their historical transactional data with Dataverse long term retention."
 ms.custom: 
-ms.date: 02/13/2024
+ms.date: 02/28/2024
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "kagoswami"
@@ -19,7 +19,7 @@ search.audienceType:
 More information: [Dataverse long term data retention overview](../../maker/data-platform/data-retention-overview.md), [Enable a table for long term retention](../../maker/data-platform/data-retention-set.md#enable-a-table-for-long-term-retention)
 
 > [!IMPORTANT]
-> To use all long term data retention features you must meet both of the requirements described here: [Dataverse long term data retention overview (preview)](../../maker/data-platform/data-retention-overview.md#dataverse-long-term-data-retention-overview-preview).
+> To use all long term data retention features you must meet both of the requirements described here: [Dataverse long term data retention overview](../../maker/data-platform/data-retention-overview.md#dataverse-long-term-data-retention-overview).
   
 ## Retention policy setup and validation
 

powerapps-docs/developer/data-platform/long-term-retention.md

@@ -1971,7 +1971,7 @@
       href: ./data-platform/data-platform-import-export.md
     - name: "Configure tables to use Copilot"
       href: ./data-platform/table-settings-for-copilot.md  
-    - name: Long term data retention for tables (preview)
+    - name: Long term data retention for tables
       items:
       - name: Long term data retention overview
         href: ./data-platform/data-retention-overview.md
@@ -2147,7 +2147,7 @@
         href: ./data-platform/export-solutions.md
       - name: Import solutions
         href: ./data-platform/import-update-export-solutions.md
-      - name: Set the preferred solution (preview)
+      - name: Set the preferred solution
         href: ./data-platform/preferred-solution.md
       - name: Use pipelines to simplify solution deployment
         href: ./data-platform/use-pipelines.md

powerapps-docs/maker/TOC.yml

@@ -6,19 +6,13 @@ ms.author: gned
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to 
-ms.date: 10/20/2023
+ms.date: 02/29/2024
 ms.custom: template-how-to 
 ---
-# Manage data retention policies (preview)
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# Manage data retention policies
 
 Use the retention policies dashboard to view and manage retention policies. From the dashboard, view the policy run history, update policy details, deactivate, and delete a policy.
 
-> [!IMPORTANT]
-> - This is a preview feature.
-> - [!INCLUDE [cc-preview-features-definition](../../includes/cc-preview-features-definition.md)]
-
 ## View and manage retention policies
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), and then on the left navigation pane select **Retention policies**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]

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

@@ -6,20 +6,14 @@ author: pnghub
 ms.author: gned
 ms.reviewer: matp
 ms.topic: overview
-ms.date: 01/31/2024
+ms.date: 02/29/2024
 ms.custom: template-overview
 ---
-# Dataverse long term data retention overview (preview)
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# 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]
->
-> - This is a preview feature.
-> - [!INCLUDE [cc-preview-features-definition](../../includes/cc-preview-features-definition.md)]
->
 > 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.
 >

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

@@ -6,19 +6,13 @@ ms.author: gned
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to 
-ms.date: 10/20/2023
+ms.date: 02/29/2024
 ms.custom: template-how-to
 ---
-# Set a data retention policy for a table (preview)
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# Set a data retention policy for a table
 
 This article explains how to set up a data retention policy for a Microsoft Dataverse table.
 
-> [!IMPORTANT]
-> - This is a preview feature.
-> - [!INCLUDE [cc-preview-features-definition](../../includes/cc-preview-features-definition.md)]
-
 ## Prerequisites
 
 Theses prerequisites must be completed before you can set a table for long term data retention:

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

@@ -6,21 +6,15 @@ ms.author: gned
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to
-ms.date: 12/06/2023
+ms.date: 02/29/2024
 ms.custom: template-how-to 
 ---
-# View long term retained data (preview)
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# View long term retained data
 
 You can view retained data from an advanced find query or by creating a Power Automate flow. 
 
 To view retained data in an environment requires the system administrator security role or other security role membership that includes organization scope read privileges to the table.
 
-> [!IMPORTANT]
-> - This is a preview feature.
-> - [!INCLUDE [cc-preview-features-definition](../../includes/cc-preview-features-definition.md)]
-
 ## Grant privileges to view retained data
 
 Imagine an auditor requires access to long term data retained for the accounts table. To provide the auditor access, a Power Platform admin creates a new role, for example a role named *LTRAccounts Access Role* and grants organization scope read privilege to the accounts table. Then add the auditor's Power Platform user account to the security role. When the auditor's job is complete, it's a best practice to remove the auditor from the security role.

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

@@ -427,6 +427,7 @@ This section describes guidelines and the known limitations with formula columns
 - The maximum depth allowed in formula columns is 10. *Depth* is defined as the chain of formula columns referring to other formula or rollup columns.  
   - For example, `table E1, F1 =  1*2, table E2, F2 - E1*2`. In this example, the depth of F2 is 1.
 - Formula columns don't display values when the app is in mobile offline mode.
+- You can't trigger workflows or plug-ins on formula columns.
 - We don't recommend using calculated columns in formula columns and vice versa.
 - Duplicate detection rules aren't triggered on formula columns.
 - The `Now` function can be used with formula columns. `Now()` has user local behavior and `UTCNow()` has time zone independent behavior.

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

@@ -1,7 +1,7 @@
 ---
 title: "Set a preferred solution | MicrosoftDocs"
 description: "Set your preferred solution in Power Apps."
-ms.date: 10/26/2023
+ms.date: 02/29/2024
 ms.topic: conceptual
 author: Mattp123
 ms.subservice: dataverse-maker
@@ -14,25 +14,16 @@ ms.custom:
   - ai-gen-desc
   - ai-seo-date:10/17/2023
 ---
-# Set the preferred solution (preview)
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# Set the preferred solution
 
 By default, unless already in the context of an unmanaged solution, all solution components are stored in the solution named Common Data Services Default Solution. Because there's no separation of components between makers and the Common Data Services Default Solution can't be exported for import to other environments, this typically isn't the best model.
 
-Using preferred solutions is a way to set which solution will support each maker's edits that happen anywhere in Power Apps. It enables makers to view and update which solution they are using. After you set your preferred solution, you can create components in the solution you specify and those components will automatically be in that solution so that you control the components within the solution. Then, you can export your preferred solution and import the solution to other Microsoft Dataverse environments.
-
-> [!IMPORTANT]
->
-> - This is a preview feature.
-> - [!INCLUDE [cc-preview-features-definition](../../includes/cc-preview-features-definition.md)]
+Using preferred solutions is a way to set which solution will support each maker's edits that happen anywhere in Power Apps. It enables makers to view and update which solution they're using. After you set your preferred solution, you can create components in the solution you specify and those components will automatically be in that solution so that you control the components within the solution. Then, you can export your preferred solution and import the solution to other Microsoft Dataverse environments.
 
 ## Prerequisites
 
 Power Platform admins enable the ability for makers to set their preferred solution by setting **Preferred solution** to **On** for the environment settings in the Power Platform admin center. More information: [Preferred solution](/power-platform/admin/settings-features#preferred-solution)
 
-<!-- Alternatively, Power Platform admins can use Dataverse APIs, so that a maker’s solution components are organized. -->
-
 > [!IMPORTANT]
 > We recommend that admins also enable the **Cloud flows** environment setting in Power Platform. Enabling this feature ensures cloud flows are also stored in Dataverse and that they're added to the maker's preferred solution. More information: [Create new canvas apps and cloud flows in a Dataverse solution](/power-platform/admin/settings-features#create-new-canvas-apps-and-cloud-flows-in-a-dataverse-solution)
 
@@ -59,7 +50,7 @@ You can delete your preferred solution or a preferred solution that other makers
 
 - You can't set or view the preferred solution in the classic solution explorer.
 - Components that are created in the classic solution explorer won't go into the preferred solution.
-- Preferred solution currently doesn't work with cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, and canvas apps created from image or a figma design.
+- Preferred solution currently doesn't work with cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, and canvas apps created from image or a Figma design.
 - When a component is already part of an existing unmanaged solution, it will still be added to the preferred solution.
 
 ### See also