Merge pull request #7002 from MicrosoftDocs/main

updating working

Author: mduelae

powerapps-docs/developer/data-platform/api-limits.md

@@ -1,14 +1,12 @@
 ---
 title: "Service protection API limits (Microsoft Dataverse) | Microsoft Docs" 
-description: "Understand the service protection limits for API requests." 
-ms.custom: ""
-ms.date: 09/14/2022
-ms.reviewer: "jdaly"
-ms.topic: "article"
-author: "divka78" 
+description: "Understand what a developer needs to do to manage service protection limits for API requests." 
+ms.date: 09/15/2022
+ms.reviewer: jdaly
+ms.topic: article
+author: divka78
 ms.subservice: dataverse-developer
-ms.author: "jdaly" 
-manager: "ryjones" 
+ms.author: dikamath 
 search.audienceType: 
   - developer
 search.app: 
@@ -251,61 +249,39 @@ If you are using the Web API with a client library, you may find that it support
 If you have written your own library, you can include behaviors to be similar to the one included in this sample code for a helper [WebAPIService class library (C#)](webapi/samples/webapiservice.md).
 
 ```csharp
-private async Task<HttpResponseMessage> SendAsync(
-    HttpRequestMessage request,
-    HttpCompletionOption httpCompletionOption = HttpCompletionOption.ResponseHeadersRead,
-    int retryCount = 0)
+/// <summary>
+/// Specifies the Retry policies
+/// </summary>
+/// <param name="config">Configuration data for the service</param>
+/// <returns></returns>
+static IAsyncPolicy<HttpResponseMessage> GetRetryPolicy(Config config)
 {
-    HttpResponseMessage response;
-    try
-    {
-        //The request is cloned so it can be sent again.
-        response = await httpClient.SendAsync(request.Clone(), httpCompletionOption);
-    }
-    catch (Exception)
-    {
-        throw;
-    }
-
-    if (!response.IsSuccessStatusCode)
-    {
-        if ((int)response.StatusCode != 429)
-        {
-            //Not a service protection limit error
-            throw ParseError(response);
-        }
-        else
-        {
-            // Give up re-trying if exceeding the maxRetries
-            if (++retryCount >= config.MaxRetries)
-            {
-                throw ParseError(response);
-            }
-
+    return HttpPolicyExtensions
+      .HandleTransientHttpError()
+      .OrResult(httpResponseMessage => httpResponseMessage.StatusCode == System.Net.HttpStatusCode.TooManyRequests)
+      .WaitAndRetryAsync(
+         retryCount: config.MaxRetries,
+         sleepDurationProvider: (count, response, context) =>
+         {
             int seconds;
-            //Try to use the Retry-After header value if it is returned.
-            if (response.Headers.Contains("Retry-After"))
+            HttpResponseHeaders headers = response.Result.Headers;
+
+            if (headers.Contains("Retry-After"))
             {
-                seconds = int.Parse(response.Headers.GetValues("Retry-After").FirstOrDefault());
+               seconds = int.Parse(headers.GetValues("Retry-After").FirstOrDefault());
             }
             else
             {
-                //Otherwise, use an exponential backoff strategy
-                seconds = (int)Math.Pow(2, retryCount);
+               seconds = (int)Math.Pow(2, count);
             }
-            await Task.Delay(TimeSpan.FromSeconds(seconds));
-
-            return await SendAsync(request, httpCompletionOption, retryCount);
-        }
-    }
-    else
-    {
-        return response;
-    }
+            return TimeSpan.FromSeconds(seconds);
+         },
+         onRetryAsync: (_, _, _, _) => { return Task.CompletedTask; }
+      );
 }
 ```
 
-You may also want to use [Polly](https://github.com/App-vNext/Polly), a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner.
+This example uses [Polly](https://github.com/App-vNext/Polly), a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner.
 
 ### HTTP Response headers
 

powerapps-docs/developer/data-platform/webapi/media/setup-postman-whoami-url.PNG

@@ -4,9 +4,9 @@ description: Includes description and supported parameters for the form OnSave e
 ms.author: jdaly
 author: adrianorth
 manager: kvivek
-ms.date: 06/24/2022
+ms.date: 09/15/2022
 ms.reviewer: jdaly
-ms.topic: "reference"
+ms.topic: reference
 applies_to: "Dynamics 365 (online)"
 search.audienceType: 
   - developer
@@ -27,7 +27,9 @@ The `OnSave` event occurs when:
 - Code executes the [formContext.data.save](../formContext-data/save.md) method and there is unsaved data in the form.
 - Code executes the [formContext.data.refresh](../formContext-data/refresh.md) method passing a true value as the first parameter and there is unsaved data in the form.
 
-To determine which button was clicked to perform the save, use the getSaveMode method.
+[!INCLUDE [cc_book-instead-of-save](../../../../../includes/cc_book-instead-of-save.md)]
+
+To determine which button was clicked to perform the save, use the [getSaveMode method](../save-event-arguments/getSaveMode.md) method.
 
 You can cancel the save action by using the preventDefault method within the event arguments object. The preventDefault method is accessible by using the getEventArgs method that is part of the execution context. Execution context is automatically passed to the form event handler.
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/events/form-onsave.md

@@ -3,10 +3,9 @@ title: "Grid OnSave event (Client API reference) in model-driven apps| Microsoft
 description: Includes description and supported parameters for the grid OnSave event.
 ms.author: jdaly
 author: adrianorth
-manager: kvivek
-ms.date: 03/12/2022
+ms.date: 09/15/2022
 ms.reviewer: jdaly
-ms.topic: "reference"
+ms.topic: reference
 applies_to: "Dynamics 365 (online)"
 search.audienceType: 
   - developer
@@ -21,7 +20,7 @@ contributors:
 The `OnSave` event occurs before sending the updated information to the server, and when any of the following occurs: 
 
 - There is a change in the record selection.
-- The user explicitly triggers a save operation using the editable grid’s save button.
+- The user explicitly triggers a save operation using the editable grid's save button.
 - The user applies a sort, filter, group, pagination, or navigation operation from the editable grid while there are pending changes.
 
 Some important points to consider for the `OnSave` event: 
@@ -33,7 +32,10 @@ Some important points to consider for the `OnSave` event:
 - Editable grid control does not implement an auto-save timer.
 Editable grid suppresses duplicate detection rules.
 
+[!INCLUDE [cc_book-instead-of-save](../../../../../includes/cc_book-instead-of-save.md)]
+
 ### Related topic
+
 [Form OnSave Event](form-onsave.md)
 
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/events/grid-onsave.md

@@ -4,9 +4,9 @@ description: Information about PostSave event methods.
 ms.author: jdaly
 author: adrianorth
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 09/15/2022
 ms.reviewer: jdaly
-ms.topic: "reference"
+ms.topic: reference
 applies_to: "Dynamics 365 (online)"
 search.audienceType: 
   - developer
@@ -21,6 +21,8 @@ contributors:
 
 PostSave event occurs after the `OnSave` event is complete. This event is used to support or execute custom logic using web resources to perform after `Save` actions when the `save` event is successful or failed due to server errors.
 
+[!INCLUDE [cc_book-instead-of-save](../../../../../includes/cc_book-instead-of-save.md)]
+
 Use the [addOnPostSave](../controls/addOnPostSave.md) and [removeOnPostSave](../controls/removeOnPostSave.md) methods to manage event handlers for this event.
 
 > [!NOTE]

powerapps-docs/developer/model-driven-apps/clientapi/reference/events/postsave.md

@@ -0,0 +1,2 @@
+> [!NOTE]
+> The `OnSave` event for appointment, recurring appointment, or service activity records will cancel the save operation and use the `Book` message to persist the change rather than `Create` or `Update`. Because of this, `OnSave` and `PostSave` event handlers for these tables will not work.

powerapps-docs/includes/cc_book-instead-of-save.md

@@ -221,6 +221,8 @@
     href: ./canvas-apps/intro-maker-portal.md
   - name: Find it with unified search
     href: search.md
+  - name: Get help from a virtual agent
+    href: ./common/virtual-agent.md 
 - name: Canvas apps
   items:
   - name: Canvas apps

powerapps-docs/maker/TOC.yml

@@ -18,7 +18,6 @@ contributors:
 ---
 # Understand Power Apps Studio
 
-[This article is pre-release documentation and is subject to change.]
 
 When you create a canvas app by using any method, you're taken to the canvas app
 builder called Power Apps Studio. You can use Power Apps Studio to design, build, and manage your canvas app. 
@@ -46,9 +45,12 @@ menu item for authoring the app.
 
 1. [Properties pane](#8--properties-pane) - properties list for the selected object in UI format.
 
-1. [Screen selector](#9--screen-selector) - switch between different screens in an app.
+1. [Virtual agent](#9--virtual-agent) - get help building your app from a virtual agent.
+
+1. [Screen selector](#10--screen-selector) - switch between different screens in an app.
+
+1. [Change canvas screen size](#11--change-canvas-screen-size) - change the size of the canvas during an authoring experience in Power Apps Studio.
 
-1. [Change canvas screen size](#10--change-canvas-screen-size) - change the size of the canvas during an authoring experience in Power Apps Studio.
 
 Let's understand each option in Power Apps Studio in detail.
 
@@ -62,31 +64,12 @@ options are relevant to the current session and app-related settings.
 > ![Power Apps Studio options.](media/studio/pa-studio-options.png)
 
 
-### Modern command bar (preview)
+### Modern command bar
 
 The modern command bar displays the relevant set of commands depending on the control that is selected. 
 
 ![This image shows how the command bar changes depending which control is selected.](media/studio/pa-studio-command-bar.gif)
 
-> [!IMPORTANT]
-> - This feature is being rolled out and depending on your region, it may not be available for your tenant yet.
-> - This is a preview feature.
-> - 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.
-
-#### Enable the modern command bar
-
-The modern command bar needs to be enabled manually through the feature switch. To enable the feature:
-
-1. Open a [new](data-platform-create-app.md) or an [existing](edit-app.md) app in Power Apps Studio.
-
-1. Select **Settings** at the top.
-
-1. Select **Upcoming features**.
-
-1. Under the **Preview** tab, set the toggle to **On** for **Enable modern command bar**.
-
-   > [!div class="mx-imgBorder"] 
-   > ![Enable the modern command bar.](media/studio/pa-studio-enable-modern-bar.png)
 
 The command bar changes when one of the following control or object is selected: 
 
@@ -467,12 +450,17 @@ selected object on the canvas. The **Properties** tab shows generic options such
 > [!div class="mx-imgBorder"] 
 > ![Properties pane.](media/studio/pa-studio-prop-pane.png)
 
-## 9 – Screen selector
+
+## 9 – Virtual agent
+
+Real-time, in-product help is available from the documentation using the Power Platform virtual agent. The virtual agent can help answer questions about common scenarios. More information: [Get help building your app from a virtual agent](../common/virtual-agent.md).
+
+## 10 – Screen selector
 
 Use the screen selector to switch between screens when your canvas app has multiple screens. You can also select a screen from the left pane by selecting the
 tree view. If the current selection is inside a container, or inside an individual cell in a gallery, the selector shows the breadcrumbs for the parent elements at each level.
 
-## 10 – Change canvas screen size
+## 11 – Change canvas screen size
 
 You can zoom in or zoom out while authoring the canvas app. Select **Ctrl**+**0**
 **Fit to window** to fit the screen size