Merge branch 'main' into DanaMartens-patch-5

sericks007 · web-flow · commit e2f0e883a32e · 2023-06-29T12:04:34.000-05:00
diff --git a/powerapps-docs/developer/data-platform/optional-parameters.md b/powerapps-docs/developer/data-platform/optional-parameters.md
@@ -1,7 +1,7 @@
 ---
 title: "Use optional parameters (Microsoft Dataverse) | Microsoft Docs" 
 description: "Use optional parameters to control operation behaviors" 
-ms.date: 05/27/2023
+ms.date: 06/28/2023
 ms.reviewer: jdaly
 ms.topic: article
 author: divkamath
@@ -222,6 +222,9 @@ More information:
 
 Use the `tag` parameter to include a shared variable value that is accessible within a plug-in. This extra information allows a plug-in to apply logic that depends on the client application.
 
+> [!NOTE]
+> This parameter is intended for client applications to be able to set any value they wish. No Microsoft feature should require that you set a specific value in your client application code to enable different behaviors.
+
 To access the value in a plug-in, use the [IExecutionContext.SharedVariables collection](xref:Microsoft.Xrm.Sdk.IExecutionContext.SharedVariables)
 
 ```csharp
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/create-app-side-panes.md b/powerapps-docs/developer/model-driven-apps/clientapi/create-app-side-panes.md
@@ -91,6 +91,26 @@ Xrm.App.sidePanes.createPane({
 > [!div class="mx-imgBorder"] 
 > ![Screenshot showing an Active Reservations list opened to an individual record.](../media/app-side-panes-opening-record.png "Open record")
 
+### Showing a web resource
+
+This example shows how to display a webresource in the side pane. A custom html page is opened in a side pane where the default header is visible & close button is hidden.
+
+```javascript
+Xrm.App.sidePanes.createPane({
+                        title: "Registration Page",
+                        imageSrc: "WebResources/msfp_SurveyIcon_32",
+                        paneId: "RegistrationPage",
+                        canClose: false
+                    }).then((pane) => {
+                        //navigate to webresource
+                        pane.navigate({
+                            pageType: "webresource",
+                            webresourceName: "new_RegistrationPage",
+                        })
+                    });
+```
+
+
 ### Managing side panes
 
 In addition to creating side panes and showing rows or views within the side pane, you can also: 
diff --git a/powerapps-docs/maker/TOC.yml b/powerapps-docs/maker/TOC.yml
@@ -75,6 +75,8 @@
         href: ../user/screen-reader.md
       - name: Keyboard shortcuts
         href: ../user/keyboard-shortcuts.md
+      - name: About dialog
+        href: ../user/about-dialog.md
     - name: Work with rows 
       items:
       - name: Create a row
@@ -1324,6 +1326,12 @@
       href: ./model-driven-apps/build-app-three-steps.md            
     - name: Explore sample apps
       href: ./model-driven-apps/overview-model-driven-samples.md
+    - name: Release channels for model-driven apps
+      items:
+      - name: Release channel overview
+        href: ./model-driven-apps/channel-overview.md
+      - name: Change release channels
+        href: ./model-driven-apps/channel-change.md
     - name: Meet the model-driven designers
       href: ./model-driven-apps/model-driven-designers.md      
   - name: Design and build an app
diff --git a/powerapps-docs/maker/canvas-apps/add-manage-connections.md b/powerapps-docs/maker/canvas-apps/add-manage-connections.md
@@ -87,11 +87,11 @@ In the list of connections, find the connection that you want to update or delet
 
 ## Manage the consent dialog appearance for custom connectors using Azure Active Directory OAuth
 
-By default, when end-users launch Power Apps apps they’re presented a connection consent dialog before they’re able to access the app experience for the first time. It’s possible for admins to suppress this consent dialog for select connectors: Microsoft First Party connectors (like SharePoint, Office 365 Users) and custom connectors using OAuth.
+By default, when end-users launch Power Apps apps they’re presented a connection consent dialog before they’re able to access the app experience for the first time. It’s possible for admins to suppress this consent dialog for select connectors: Microsoft First Party connectors (like SharePoint, Office 365 Users) and custom connectors using Azure Active Directory (Azure AD) OAuth.
 
-### Suppress consent dialog for apps that use custom connectors using OAuth
+### Suppress consent dialog for apps that use custom connectors using Azure AD OAuth
 
-To suppress consent dialog for apps created using Power Apps that connect through custom connectors using OAuth, follow the below steps.
+To suppress consent dialog for apps created using Power Apps that connect through custom connectors using Azure AD OAuth, follow the below steps.
 
 #### Step 1. Provision Microsoft’s Azure API connections service principal in your Azure AD tenant
 
@@ -143,7 +143,7 @@ In addition to the admin consent granted on a custom application in Azure AD, wh
   Set-AdminPowerAppApisToBypassConsent -AppName <Power Apps app id>
 ```
 
-### Remove consent suppression for apps that use custom connectors using OAuth
+### Remove consent suppression for apps that use custom connectors using Azure AD OAuth
 
 To remove consent suppression for a custom connector, an admin must perform at least one of the following actions:
 
diff --git a/powerapps-docs/maker/canvas-apps/ai-overview.md b/powerapps-docs/maker/canvas-apps/ai-overview.md
@@ -54,7 +54,7 @@ The following are requirements to access the waitlist for this preview:
 
     1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
 
-    2. In the admin center, go to **Environments** &gt; *\[select an environment\]* &gt; **Settings** &gt; **Features**.
+    2. In the admin center, go to **Environments** &gt; *\[select an environment\]* &gt; **Settings** &gt; **Product** &gt; **Features**.
 
     3. On the **Features** settings page, under **AI Builder**, enable or disable **AI Builder preview models**.
 
diff --git a/powerapps-docs/maker/model-driven-apps/channel-change.md b/powerapps-docs/maker/model-driven-apps/channel-change.md
@@ -0,0 +1,86 @@
+---
+title: Changing release channels for model-driven apps | MicrosoftDocs
+description: Understand the release channels for Power Apps model-driven apps.
+author: aorth
+ms.service: powerapps
+ms.subservice: mda-maker
+ms.author: aorth
+ms.reviewer: matp
+ms.date: 06/27/2023
+ms.topic: how-to
+applies_to: 
+  - "powerapps"
+search.audienceType: 
+  - maker
+---
+# Changing release channels for model-driven apps
+
+The release channel affects the features that are shown to a user. When the monthly channel is enabled for an environment, makers need to validate that their customizations work with each monthly release. This article describes different approaches for a maker to change channels and validate an upcoming release..
+
+## Flexible channel configuration
+
+The release channel for model-driven apps can be changed in a couple different ways.
+
+- Environment channel
+- 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.
+> - The browser session channel can be applied using a URL parameter, which is a temporary override.
+
+## Changing the environment channel
+
+The environment channel can be set using the Power Platform admin center or with code.
+
+Power Platform admins can change the release channel using the environment's behavior settings. More information: [Manange behavior settings](/power-platform/admin/settings-behavior).
+
+Developers can change the release 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 is always a single row in the organization table.
+More information:
+
+* [Update a record using Web API](/power-apps/developer/data-platform/webapi/update-delete-entities-using-web-api#basic-update)
+* [Update a record using the SDK for .NET](/power-apps/developer/data-platform/org-service/entity-operations-update-delete?tabs=late#basic-update)
+
+## Changing the browser session channel
+
+A single browser session can be changed by adding the URL parameter ```&channel=<channelname>```. This URL parameter is used for all navigation within the browser tab. It might not be copied to a new browser tab.
+
+| Channel | URL parameter |
+| --- | --- |
+| Semi-annual | ```&channel=semiannual``` |
+| Monthly | ```&channel=monthly``` |
+
+When the channel is monthly, the monthly release can be changed using the URL parameter ```&channelrelease=<releasename>```. The release name is three letter month and four digit year like *MmmYYYY*.
+
+| Monthly Release | Release Name Parameter |
+| --- | --- |
+| May 2023 | ```&channelrelease=May2023``` |  
+| June 2023 | ```&channelrelease=Jun2023``` |  
+| July 2023 | ```&channelrelease=Jul2023``` |  
+| August 2023 | ```&channelrelease=Aug2023``` |  
+
+> [!NOTE]
+> Any valid ```MmmYYYY``` date can be entered but future dates might not have any features defined.  
+
+## Validating the next monthly release
+
+Validation should be done for each monthly channel release before it's automatically enabled for users. Users can test when the validation build version has reached the environment.
+
+1. Find the current monthly release a model-driven app by selecting **Settings** > **About**. The release version follows **Channel: Monthly** and is a date like *July 2023*.
+
+1. Find the next monthly release short name by opening [Unified Interface monthly channel releases](/power-platform/released-versions/common-data-service/unified-interface-monthly-releases)
+
+1. Add the URL parameter ```&channelrelease=``` with the next release short name like *Aug2023*.
+
+## Comparing features across channels and releases
+
+When a user running the monthly channel report observes unexpected behavior, the following steps can help investigate where the behavior occurred.
+
+- Check if the unexpected behavior exists in the semi-annual channel by using the URL parameter ```&channel=semiannual```. If the behavior also exists in the semi-annual channel, it's unrelated to the monthly channel and should follow normal support processes.
+- Check if the unexpected behavior exists in the previous monthly release by using the URL parameter ```&channelrelease=``` with the prior release short name like *Jun2023*. If the two monthly releases behave the same, then it's likely unrelated to a specific monthly channel release and should follow normal support processes.
+- When a change is noticed between monthly releases, review the changed features in [Unified Interface monthly channel releases](/power-platform/released-versions/common-data-service/unified-interface-monthly-releases) to learn more.
+
+## See also
+
+[Release channel overview](channel-overview.md) <br />
+[User About dialog - channel](../../user/about-dialog.md) <br />
+[Power Platform admin center - Manage behavior settings](/power-platform/admin/settings-behavior)
diff --git a/powerapps-docs/maker/model-driven-apps/channel-overview.md b/powerapps-docs/maker/model-driven-apps/channel-overview.md
@@ -0,0 +1,58 @@
+---
+title: "Release channel for your model-driven app | MicrosoftDocs" 
+description: "This article outlines how release channels enable features within a model-driven app."
+ms.custom: ""
+ms.date: 06/27/2023
+ms.reviewer: "matp"
+ms.service: powerapps
+ms.subservice: mda-maker
+ms.topic: overview
+author: "aorth"
+ms.author: "aorth"
+search.audienceType: 
+  - maker
+---
+# Release channels for your model-driven app
+
+Microsoft provides new (and updated) features for your model-driven apps, on a regular basis. You can control how often the users in your organization get these new features by specifying the release channel. The concept of multiple release channels originated from [Microsoft 365 channels](/deployoffice/updates/overview-update-channels) and provides Power Platform admins with a choice of how often end user impacting features are released.
+
+Environment admins use the Power Platform admin center to select the channel for the environment. The existing cadence of twice-yearly release waves is called the *Semi-annual channel* and is the default for all existing orgs. The new *monthly channel* option enables GA-ready features to be turned on each month with a four week preview notification period to allow customer validation with existing customizations.
+
+The following table provides a comparison of monthly channel and semi-annual channel.
+
+| Category | Monthly channel | Semi-annual channel |
+| --- | --- | --- |
+| Recommended use | Provide your users with new end user impacting features only once a month and on a predictable schedule. | For users in your organization where more training and extensive testing are needed before rollout out of new end user impacting features. | 
+| Release frequency | Once a month, on the first release for the month and following the gradual weekly rollout. | Twice a year, starting early April and early October and following the gradual weekly rollout. |
+
+Security and non-end user impacting changes continue to be delivered with the weekly releases and changes outlined in [Microsoft Unified Interface versions](/power-platform/released-versions/powerapps#all--microsoft-unified-interface-versions).
+
+The key idea is that GA-ready end user impacting features release monthly instead of waiting for the twice-yearly release cadence. The same number of features are delivered in twelve smaller releases instead of two larger releases.
+
+Microsoft 365 products have seen a consistently higher user satisfaction for monthly channel compared to the semi-annual channel. Currently, we observe a user satisfaction drop with the twice-yearly releases, and we're looking to improve this experience by following the Microsoft 365 channel approach.
+
+## Monthly release schedule
+
+Model-driven apps release updates every week, which are gradually rolled out to groups of regions over several weeks. Below are the region groups with each group happening in successive weekend updates.
+
+1. First release environment (FRE)
+1. Canada, South America, India, France, South Africa, Germany, Switzerland, Norway, Korea, Singapore
+1. United Arab Emirates, Japan, Asia Pacific, Great Britain, Australia
+1. Europe
+1. United States
+
+The monthly release is the first weekly release of each month. The release matches ```YYMM.1``` where ```YY``` is the release year and ```MM``` is the release month. The monthly release notes are published to [Released versions for Power Apps](/power-platform/released-versions/powerapps) four weeks before the release reaches the region group 2. Region group 2 is used because it's the first region group for production customer environments and region group 1 is used for customer early validation.
+
+| Monthly release | Doc published | Feature release | Group 1 | Group 2 | Group 3 | Group 4 | Group 5 | 
+| --- | --- | --- | --- | --- | --- | --- | --- | 
+| May 2023 | Apr 14 | 2305.1 | May 5 | May 12 | May 19 | May 26 | Jun 2 |
+| June 2023 |  May 19 | 2306.1 | Jun 9 | Jun 16 | Jun 23 | Jun 30 | Jul 7 |
+| July 2023 | Jun 16 | 2307.1 | Jul 7 | Jul 14 | Jul 21 | Jul 28 | Aug 4 |
+| August 2023 | Jul 21 | 2308.1 | Aug 11 | Aug 18 | Aug 25 | Sep 1 | Sep 8 |
+| September 2023 | Aug 18 | 2309.1 | Sep 8 | Sep 15 | Sep 22 | Sep 29 | Oct 6 |
+
+## See also
+
+[Changing release channels](channel-change.md) <br />
+[User about dialog - channel](../../user/about-dialog.md) <br />
+[Power Platform admin center - Manage behavior settings](/power-platform/admin/settings-behavior)
diff --git a/powerapps-docs/maker/model-driven-apps/media/model-app-channels/ppac-settings-behavior-change-channel.png b/powerapps-docs/maker/model-driven-apps/media/model-app-channels/ppac-settings-behavior-change-channel.png
diff --git a/powerapps-docs/mobile/offline-sync-icon.md b/powerapps-docs/mobile/offline-sync-icon.md
@@ -1,7 +1,7 @@
 ---
 title: View offline sync status
 description: Learn how to interpret the offline sync icon in the mobile app navigation bar.
-ms.date: 02/08/2023
+ms.date: 06/05/2023
 ms.author: sericks
 author: sericks007
 ms.reviewer: 
@@ -39,6 +39,19 @@ The offline sync icon changes based on the app's sync status. The following tabl
 | ![Icon showing that the synchronization process encountered an error.](media/error.png "Icon showing that the synchronization process encountered an error.") | The synchronization process encountered an error. |
 | ![Icon showing that the synchronization process encountered a warning.](media/warning.png "Icon showing that the synchronization process encountered a warning.") | The synchronization process encountered a warning. |
 
+## Types of offline syncs
+Data is synchronized from Dataverse to your device over the lifetime of your app using several synchronization modes.
+
+- **First sync** - This sync is the initial offline sync that occurs for the Power Apps mobile app. All data in the offline profile is downloaded to the device. A user must use the Power Apps mobile app in online mode until the first sync is completed.
+
+  The first sync, which is the longest sync, is triggered when you sign-in to the Power Apps mobile app. It is also triggered after using the Reconfigure action (not recommended).
+
+- **Delta sync** - This sync is the fastest sync, and occurs regularly based on the offline configuration for the organization. For example, a delta sync could occur every five minutes. Only data that has changed since the last sync occurred is downloaded to the mobile device.
+
+- **Full delta sync** - When you select **Refresh** on the **Device status** page, you trigger a full sync. A full sync doesn't redownload data, but it does recheck every record on the device, so it may take longer than a regular delta sync.
+
+- **Grid sync** - If you select **Refresh** on a grid or calendar view, the app will immediately synchronize all tables visible in the view. When the sync is complete, the view will refresh automatically.
+
 ## Offline Status page
 
 When you select the offline sync icon, the **Offline Status** page opens. The **Offline Status** page provides details such as what data was downloaded, whether there is data waiting to upload, and the amount of storage the app is using.
diff --git a/powerapps-docs/user/about-dialog.md b/powerapps-docs/user/about-dialog.md
@@ -0,0 +1,35 @@
+---
+title: "About dialog for model-driven apps | MicrosoftDocs"
+description: Learn about the various parts of the About dialog for model-driven apps.
+author: sericks007
+ms.component: pa-user
+ms.topic: conceptual
+ms.date: 06/27/2023
+ms.subservice: end-user
+ms.author: sericks
+ms.reviewer: ""
+ms.assetid: 
+search.audienceType: 
+  - enduser
+contributors:
+- adrianorth
+---
+
+#  About dialog for model-driven apps 
+
+This article explains the various parts of the **About** dialog for model-driven apps.
+
+:::image type="content" source="media/about-dialog/about-dialog-channel.png" alt-text="About dialog for model-driven apps.":::
+
+- The **Channel** attribute indicates the feature set being used. Admins can set a channel value of **Semi-annual** or **Monthly** in the Power Platform admin center or through code. More information: [Manage behavior settings](/power-platform/admin/settings-behavior)
+
+- The **semi-annual channel** is the current, twice-a-year release wave that is updated in April and October. The release for the semi-annual channel is shown at the top of the dialog like **2023 release wave 1 enabled**.
+
+- The **monthly channel** is the new, release cadence that happens once per month. The release for the monthly channel is shown after **Channel: Monthly** as a month and year. For example, in the screenshot provided, the monthly channel is May 2023.
+
+
+## See also
+* [Release Channels for your model driven app](../maker/model-driven-apps/channel-overview.md)
+* [Changing release channels for model-driven apps](../maker/model-driven-apps/channel-change.md)
+
+[!INCLUDE[footer-include](../includes/footer-banner.md)]
diff --git a/powerapps-docs/user/collaboration.md b/powerapps-docs/user/collaboration.md
@@ -1,12 +1,12 @@
 ---
 title: "Collaborate with others in model-driven apps| MicrosoftDocs"
 description: Collaborate with others in model-driven apps
-author: fikaradz 
+author: sriharibs-msft
 ms.component: pa-user
 ms.topic: conceptual
 ms.date: 06/29/2023
 ms.subservice: end-user
-ms.author: fikaradz
+ms.author: srihas
 ms.custom: ""
 ms.reviewer: sericks
 ms.assetid: 
diff --git a/powerapps-docs/user/media/about-dialog/about-dialog-channel.png b/powerapps-docs/user/media/about-dialog/about-dialog-channel.png
diff --git a/powerapps-docs/whats-new.md b/powerapps-docs/whats-new.md
