Merge branch 'main' into users/tahoon/no-date-only

Author: Mattp123

powerapps-docs/developer/data-platform/bypass-custom-business-logic-preview.md

@@ -287,7 +287,7 @@ Use this FetchXml query to return `step.sdkmessageprocessingstepid` values you c
 
 ### Limit to the number of steps
 
-To ensure that the parameter size isn't too large, the default limit on the number of steps you can pass is three. The limit is controlled using data in the [Organization table OrgDbOrgSettings column](reference/entities/organization.md#BKMK_OrgDbOrgSettings). Don't try to edit this value yourself. Use the [OrgDBOrgSettings tool for Microsoft Dynamics CRM](https://support.microsoft.com/topic/orgdborgsettings-tool-for-microsoft-dynamics-crm-20a10f46-2a24-a156-7144-365d49b842ba) or [OrgDbOrgSettings app](https://github.com/seanmcne/OrgDbOrgSettings?tab=readme-ov-file#where-to-find-the-releases) to change the `BypassBusinessLogicExecutionStepIdsLimit` value.
+To ensure that the parameter size isn't too large, the default limit on the number of steps you can pass is three. The limit is controlled using data in the [Organization table OrgDbOrgSettings column](reference/entities/organization.md#BKMK_OrgDbOrgSettings). Use the [OrgDBOrgSettings tool for Microsoft Dynamics CRM](https://support.microsoft.com/topic/orgdborgsettings-tool-for-microsoft-dynamics-crm-20a10f46-2a24-a156-7144-365d49b842ba) or [OrgDbOrgSettings app](https://github.com/seanmcne/OrgDbOrgSettings?tab=readme-ov-file#where-to-find-the-releases) to change the `BypassBusinessLogicExecutionStepIdsLimit` value.
 
 The maximum recommended size for this limit is 10 steps.
 

powerapps-docs/maker/data-platform/data-retention-faq.yml

@@ -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.
 

powerapps-docs/maker/data-platform/update-solutions.md

@@ -67,6 +67,9 @@ The procedure to import the updated solution is similar to installing a new mana
 **Completing Solution Upgrade**
 If you chose to stage for upgrade, or if the system had an issue completing an upgrade, you'll see that you have the original solution still installed in your system as well as a new solution that has the same solution name as the base solution suffixed with \_Upgrade.  To complete the upgrade, select the base solution in the solution list and select **Apply Solution Upgrade**.  This uninstalls all previous patches and the base solution then rename the \_Upgrade solution to be the same name as the previous base solution.  Any components that were in the original solution and patches that aren't present in the \_Upgrade solution will be deleted as part of this process.
 
+> [!NOTE]
+> Recent changes in the platform have optimized the single step upgrade process to no longer use a temporary _Upgrade solution or use an uninstall operation on the original solution.
+
 ## Understanding version numbers for updates
 
 A solution's version has the following format: major.minor.build.revision. An update must have a higher major, minor, build, or revision number than the parent solution. For example, for a base solution version 3.1.5.7, a small update could be a version 3.1.5.8 or a slightly more significant update could have version 3.1.7.0. A substantially more significant update could be version 3.2.0.0.

powerapps-docs/maker/model-driven-apps/channel-change.md

@@ -6,7 +6,7 @@ ms.service: powerapps
 ms.subservice: mda-maker
 ms.author: aorth
 ms.reviewer: matp
-ms.date: 04/03/2024
+ms.date: 05/29/2024
 ms.topic: how-to
 applies_to: 
   - "powerapps"
@@ -23,13 +23,13 @@ The release channel affects the features that impact users. When the monthly cha
 
 The release channel for model-driven apps can be changed in two primary ways.
 
-- App channel (starting with build 23111)
+- App channel
 - Environment channel
 
 In addition, the release channel can be overridden with either of these options.
 
-- [User channel override](/power-platform/admin/user-channel-override) (starting with build 23111)
-- Browser session channel
+- [User channel override](/power-platform/admin/user-channel-override)
+- [Browser session channel override](#changing-the-browser-session-channel)
 
 > [!NOTE]
 > When the release channel is changed on the environment level, a user must refresh the browser tab twice to update the release channel information. The first refresh triggers a background update of feature configuration to a local cache. The second refresh uses the feature configuration local cache.
@@ -38,6 +38,12 @@ In addition, the release channel can be overridden with either of these options.
 
 The environment channel can be set using the Power Platform admin center or with code.
 
+| Environment release channel | Environment setting value | Behavior |
+|--|--|--|
+| Auto | 0 | Environment default value is currently **Semi-annual**, but will change to **Monthly** with 2024 release wave 2. |
+| Monthly | 1 | Environment explicitly set to **Monthly Channel**. |
+| Semi-annual | 3 | Environment explicitly set to **Semi-Annual Channel**. |
+
 Power Platform admins can change the release channel using the environment's behavior settings. More information: [Manage behavior settings](/power-platform/admin/settings-behavior).
 
 Developers can change the environment channel by updating the [ReleaseChannel](/power-apps/developer/data-platform/reference/entities/organization#BKMK_ReleaseChannel) column value for the row in the [Organization](/power-apps/developer/data-platform/reference/entities/organization) table. There's always a single row in the organization table.
@@ -52,7 +58,7 @@ The app channel can be used to override the release channel for a model-driven a
 
 | App release channel | App setting value | Behavior |
 |--|--|--|
-| Auto | 0 | App default value is **Semi-annual**, but will later change to **Monthly** in a future release wave. |
+| Auto | 0 | App default value is **Semi-annual** for Dynamics 365 orgs and **Monthly** for Power Apps orgs. With 2024 release wave 2 the default will change to **Monthly**. |
 | Monthly | 1 | App explicitly set to **Monthly Channel**. |
 | Semi-annual | 3 | App explicitly set to **Semi-Annual Channel**. |
 
@@ -104,6 +110,8 @@ A maker can use the **Solutions** area to explicitly set the release channel for
 
 As part of the gradual migration to default all apps to use monthly channel, newly created model-driven apps will gradually start seeing the app channel defaulted. Admins or makers can control the release channel default for new apps using an app setting. The app setting **Allow new app channel default** defaults to **Yes**, which means a newly created app is set to **Monthly**.
 
+To override this behavior, change the app setting to **No** in the environment or apply to multiple environments by including in a solution that is imported into the environments.
+
 ### Prevent new app default to monthly channel
 
 The new app default can be prevented by switching **Allow new app channel default** to **No**. This causes the new app to be created with release channel **Auto** value.