Pull from main

Author: Mattp123

powerapps-docs/developer/data-platform/scalable-customization-design/auto-numbering-example.md

@@ -1,20 +1,27 @@
 ---
-title: "Scalable Customization Design: Auto-numbering example (Microsoft Dataverse) | Microsoft Docs" 
+title: "Scalable Customization Design: Autonumbering example (Microsoft Dataverse) | Microsoft Docs" 
 description: "This example illustrates how transactions and concurrency issues need to be accounted for in a code customization."
-ms.date: 04/23/2024
+ms.date: 09/06/2024
 ms.reviewer: pehecke
 ms.topic: article
 author: rogergilchrist
-ms.author: jdaly # MSFT alias of Microsoft employees only
+ms.author: rogergil
 search.audienceType: 
   - developer
+contributors:
+ -JimDaly
 ---
-# Scalable Customization Design: Auto-numbering example
+# Scalable Customization Design: Autonumbering example
 
 
 
 > [!NOTE]
 > This example supports a series of topics about scalable customization design. To start at the beginning, see [Scalable Customization Design in Microsoft Dataverse](overview.md).
+>
+> Dataverse has an [Autonumber columns](../../../maker/data-platform/autonumber-fields.md) feature you should use if it meets your requirements.
+> 
+> This article describes how to manage transactions effectively to ensure a solution can handle growth, using the example of autonumbering. It outlines a process of trying, testing, and evaluating different approaches. While the third approach improves upon the first two, it might not be perfect for every situation. Therefore, it's crucial to thoroughly test any developed solution, as you are responsible for maintaining your own code.
+
 
 One scenario that illustrates the common misunderstanding of how transactions are handled within Dataverse is implementing an automatic numbering scheme.
 
@@ -37,12 +44,12 @@ The following sections describe different approaches that can be taken within Da
 
 ## Approach 1: Out of a transaction
 
-The simplest approach is to realize that any use of a commonly required resource would introduce the potential for blocking. Since this has an impact on scalability, you might decide you want to avoid a platform transaction when generating an auto number.
+The simplest approach is to realize that any use of a commonly required resource would introduce the potential for blocking. Since blocking has an impact on scalability, you might decide you want to avoid a platform transaction when generating an auto number.
 Let's consider the scenario for auto numbering generation outside of the pipeline transaction in a pre-validation plug-in.
 
 ![Approach 1: Out of a transaction.](media/autonumber-approach-1.png)
 
-When you run this in isolation it works fine. It doesn't, however, actually protect against concurrency errors. As the following diagram shows, if two requests in parallel both request the latest number and then both increment and update the value, you end up with duplicate numbers. Because there's no locking held against the retrieved number, it's possible for a race condition to occur and both threads to end up with the same value. 
+When you run this in isolation, it works fine. It doesn't, however, actually protect against concurrency errors. As the following diagram shows, if two requests in parallel both request the latest number and then both increment and update the value, you end up with duplicate numbers. Because there's no locking held against the retrieved number, it's possible for a race condition to occur and both threads to end up with the same value. 
 
 ![race condition.](media/autonumber-approach-1-a.png)
 
@@ -84,7 +91,7 @@ Normally, generation of the auto number would be done in a pre-event plug-in. Yo
 
 With the scalability implications in mind, if there's other complex processing in the account creation process, an alternative would be to move the auto number generation to a post create process, which still ensures a consistent update process. The benefit would be that it reduces the length of time within the transaction that the auto number record lock is held as the lock is only taken towards the end of the process. If the auto numbering table is the most highly contested resource and this approach is taken for all processes accessing it, this reduces the amount of contention overall.
 
-The tradeoff here would be the need to perform an additional update to account, while reducing the overall length of time blocking waiting for the auto numbering record.
+The tradeoff here would be the need to perform an another update to account, while reducing the overall length of time blocking waiting for the auto numbering record.
 
 ![move the auto number generation to a post create process.](media/autonumber-approach-3-b.png)
 

powerapps-docs/maker/common/faq-timeline-highlights-with-copilot.md

@@ -64,8 +64,29 @@ We used the following metrics to measure Copilot's performance:
 
 Copilot is a powerful and helpful feature, but it isn't perfect. It has some limitations that you should be aware of and respect. These limitations include: 
 
-- **Language**: Copilot only supports the English language for now. If you need to write in another language, you can't use Copilot. 
-
+- **Language**: Many languages are supported in Copilot scenarios. While the quality is expected to be highest in English, the quality in the other languages is expected to improve over time. The following languages are available for Copilot in the timeline:
+  
+   - Danish
+   - Dutch
+   - English
+   - French
+   - German
+   - Italian
+   - Japanese
+   - Portuguese (Brazil)
+   - Spanish
+   - Thai
+   - Simplified Chinese
+   - Czech
+   - Finnish
+   - Greek
+   - Korean
+   - Norwegian (Bokmål)
+   - Polish
+   - Russian
+   - Swedish
+   - Turkish
+  
 - **Suggestions**: Copilot only provides suggestions, not final content. You're responsible for reviewing and editing the content before you send it to your customers. You shouldn't rely on Copilot to write your content for you. 
 
 - **Ethics**: Copilot is designed to help you create ethical and responsible content. However, Copilot may not be able to detect or prevent offensive, harmful, or misleading content. You should always use your own judgment and follow your company's policies and values when using Copilot. 

powerapps-docs/mobile/canvas-mobile-offline-setup.md

@@ -1,7 +1,7 @@
 ---
 title: Set up mobile offline for canvas apps 
 description: Learn how to set up canvas apps for use offline on mobile devices in Microsoft Power Apps.
-ms.date: 09/09/2024
+ms.date: 09/10/2024
 ms.topic: how-to
 ms.subservice: mobile
 ms.component: pa-user
@@ -23,14 +23,15 @@ Turn on offline mode in your canvas app if users need to work without worrying a
 
 ## Prerequisites
 
-- [The canvas app must be in a solution](../maker/canvas-apps/add-app-solution.md).
-
 - You must have the Environment Maker, System Administrator, or System Customizer role to set up offline mode for canvas apps. These roles have create, read, write, delete, and share privileges on **Canvas App**, **Mobile offline profile**, and **Sync Error** tables. [Learn about predefined security roles](../maker/model-driven-apps/share-model-driven-app.md#about-predefined-security-roles).
 
 - Users with the Basic User role can't open an offline application. You must create a custom security role with read privileges on **Canvas App**, **Mobile offline profile**, and **Sync Error** tables.
 
 - If you already have a custom security role, make sure it grants read privileges on **Canvas App**, **Mobile offline profile**, and **Sync Error** tables. Learn about [Create or edit a security role to manage access](/power-platform/admin/create-edit-security-role).
 
+> [!NOTE]
+> It's recommended that the [canvas app is in a solution](../maker/canvas-apps/add-app-solution.md). The offline profile **App usage** field in the [Power Platform admin center](https://admin.powerplatform.microsoft.com/) (**Environements** > _select an environment_ > **Setings** > **User + permissions** > **Mobile configuration**) only applies to apps within a solution.  
+
 ## Optimize your app for mobile offline
 
 Mobile apps run on small screens with limited connectivity. Before you set up offline mode, make sure your canvas app is optimized for offline and mobile use. Consider the user scenarios you want to cover and the amount of data the app uses. Create an app that's simple and lightweight.

powerapps-docs/user/modern-fluent-design.md

@@ -3,7 +3,7 @@ title: Modern, refreshed look for model-driven apps
 description: Learn about the updated, user interface that makes model-driven apps easier to use.
 author: chmoncay
 ms.topic: overview
-ms.date: 09/05/2024
+ms.date: 09/10/2024
 ms.service: powerapps
 ms.subservice: end-user
 ms.author: chmoncay
@@ -91,27 +91,27 @@ Switching themes or enabling dark mode isn't supported at this time.
 
 ### Honoring classic theming
 
-With the modern, refreshed look, Power Apps is no longer honoring [classic theme customizations](../maker/model-driven-apps/create-themes-organization-branding.md). You can, however, override the colors for the app header to match your organization branding with the modern, refreshed look. See [change the color of the app header](#change-the-color-of-the-app-header) for more details.  Other theme customization options for the modern, refreshed look aren't available yet.  
+With the modern, refreshed look, Power Apps is no longer honoring [classic theme customizations](../maker/model-driven-apps/create-themes-organization-branding.md). You can, however, override the colors for the app header to match your organization branding with the modern, refreshed look. Leaern more in [Change the color of the app header](#can-i-change-the-color-of-the-app-header).  Other theme customization options for the modern, refreshed look aren't available yet.  
 
 ### Custom icons
 
 Only SVG icons are supported. If you use other formats such as PNG, the navigation doesn't display them and a default icon appears instead.
 
 ## Frequently asked questions (FAQs)
 
-### Using the modern, refreshed look in Power Apps Component Framework / custom code components
+### Can I use the modern, refreshed look in the Power Apps component framework or in custom code components?
 
 The modern theme in use is passed to [Power Apps component framework](../developer/component-framework/overview.md) components allowing you to [style your components with modern theming](../developer/component-framework/fluent-modern-theming.md).
 
-### Using the modern, refreshed look in custom pages
+### Can I use the modern, refreshed look in custom pages?
 
 Modern controls can be used with custom pages and the modern, refreshed look. The modern theme isn't currently inherited by custom pages.
 
-### Change the color of the app header
+### Can I change the color of the app header?
 
 It's possible to change the color of the app header to match your organization while in the modern, refreshed look. See [Use modern themes](../maker/model-driven-apps/modern-theme-overrides.md) for more details. Other theme customization options for the modern, refreshed look aren't available yet.
 
-### Using custom chart colors
+### Can I use custom chart colors?
 
 When using the modern, refreshed look, charts in views and dashboards are updated to a set of modern colors. If the chart colors have been customized, the new look overrides the custom colors. The maker can keep the custom colors by adding the **CustomColorOverride** property in the chart .xml file.