Merge pull request #8710 from MicrosoftDocs/main

Auto push to live 2025-04-15 02:30:46

Author: Deland-Han

support/dynamics/gp/experience-slow-performance.md

@@ -3,7 +3,7 @@ title: Experience slow performance
 description: Provides information that you can use to troubleshoot performance problems. Also contains a list of questions that you should answer before you contact a support professional.
 ms.reviewer: theley
 ms.topic: troubleshooting
-ms.date: 03/20/2024
+ms.date: 04/15/2025
 ms.custom: sap:System and Security Setup, Installation, Upgrade, and Migrations
 ---
 # You experience slow performance when you do specific processes in Microsoft Dynamics GP
@@ -138,7 +138,7 @@ We recommend the following exclusions.
 
 **On the Microsoft Dynamics GP client**  
 Exclude the Dynamics\GP folder. By default, this folder is in the following location:  
-`C:\Program Files\Microsoft Dynamics\GP`
+`C:\Program Files (x86)\Microsoft Dynamics\GP`
 
 The following file name extensions should be excluded:
 
@@ -172,7 +172,7 @@ Exclude the `*.ldf` database files, and the `*.mdf` database files.
 On any computer that is running Integration Manager  
 Exclude the .MDB or .IMD files and the Integration Manager code folder which default, this folder is in the following location:
 
-`C:\Program Files\Microsoft Dynamics\Integration Manager`
+`C:\Program Files (x86)\Microsoft Dynamics\Integration Manager`
 
 ### Performance problems that occur on the home page in Microsoft Dynamics GP
 

support/power-platform/power-apps/create-and-use-apps/common-issues-and-resolutions.md

@@ -4,7 +4,7 @@ description: A list of common issues and resolutions within Power Apps.
 author: KumarVivek
 ms.custom: sap:App Creation (Canvas App)
 ms.reviewer: tapanm, lanced, tahoon 
-ms.date: 03/26/2025
+ms.date: 04/15/2025
 ms.author: kvivek
 search.audienceType: 
   - maker
@@ -16,15 +16,15 @@ contributors:
 ---
 # Common issues and resolutions for Power Apps
 
-This article lists common issues you might encounter while using Power Apps. Issues are grouped by area, and summary-level workarounds are provided where applicable. Pointers to primary documentation locations are also provided.
+This article lists common issues you might encounter while using Power Apps. It groups issues by area and provides summary-level workarounds where applicable. Pointers to primary documentation locations are also provided.
 
 Refer to the introductory article [Power Apps troubleshooting strategies](isolate-common-issues.md) for guidance on narrowing down the source of your issue. That article outlines key principles for debugging both functional and performance issues.
 
 ## Common issue areas
 
 - [Connectors and delegation](#connectors-and-delegation)
   - [Common issues](#common-issues)
-- [Integration](#integration)
+- [Integration](#power-automate-integration)
 - [Power Fx](#power-fx)
 - [Region](#region)
 - [Studio and Forms](#studio-and-forms)
@@ -44,13 +44,13 @@ End users might encounter this issue in two situations:
 
 1. The application might have a shared implicit connection that isn't a secure implicit connection. Sharing the connection with the end user can resolve the issue but isn't recommended. All connections should be converted to secure implicit connections by the author.
 
-2. If the connection is already a secure implicit connection, republishing the app might resolve the issue. If not, a product bug should be filed.
+2. The connection in the application is already a secure implicit connection. In this case, republishing the app might resolve the issue. If not, a product bug should be filed.
 
 ### Common issues
 
 1. **Automatic Next links for galleries and grids don't work for action-based connectors.**
 
-    Next links (the property on a query result that enables a gallery or grid to automatically page in the next set of results of a query) aren't supported for action-based connectors. For a discussion of this topic, see the [Overview of connectors for canvas apps](/power-apps/maker/canvas-apps/connections-list#actions).
+    Action-based connectors don't support next links. Next links are properties on query results that allow a gallery or grid to automatically load the next set of results. For more information, see [Overview of connectors for canvas apps](/power-apps/maker/canvas-apps/connections-list#actions).
 
 1. **Sharing a Canvas app using SharePoint connector**
 
@@ -62,7 +62,13 @@ End users might encounter this issue in two situations:
 
 1. **Custom connectors and Microsoft Dataverse**
 
-    If an app created using Power Apps build 2.0.540 or earlier relies on a database in the Dataverse and at least one custom connector in a different environment, you need to deploy the connector to the same environment as the database and update the app to use the new connector. Otherwise, a dialog notifies users that the API wasn't found. For more information, see [Environments overview](/power-platform/admin/environments-overview).
+    You need to make adjustments if you built your app with Power Apps that:
+
+    1. Is version 2.0.540 or earlier.
+    2. Relies on a Dataverse database.
+    3. Uses at least one custom connector from a separate environment.
+
+    First, deploy the custom connector to the same environment as the database. Then, update the app to use the newly deployed connector. Otherwise, a dialog notifies users that the API wasn't found. For more information, see [Environments overview](/power-platform/admin/environments-overview).
 
 1. **Column names with spaces**
 
@@ -74,7 +80,7 @@ End users might encounter this issue in two situations:
 
 1. **For apps that are created from data, only the first 500 records of a data source can be accessed.**
 
-    Power Apps works with large data sources by delegating operations to the data source. For operations that can't be delegated, Power Apps will give a warning at authoring time and operate on only the first 500 records of the data source. For more information, see the [Delegation overview](/power-apps/maker/canvas-apps/delegation-overview#delegable-functions).
+    Power Apps works with large data sources by delegating operations to the data source. For operations that can't be delegated, Power Apps shows a warning at authoring time and operates on only the first 500 records of the data source. For more information, see the [Delegation overview](/power-apps/maker/canvas-apps/delegation-overview#delegable-functions).
 
 1. **Excel data must be formatted as a table.**
 
@@ -86,15 +92,29 @@ End users might encounter this issue in two situations:
 
 1. **Sign-in issues on certain Android mobile devices when using authenticator**
 
-    In certain devices and scenarios, you might experience sign-in failures when using an authenticator. This is due to the OEM limiting this functionality. For more information, see [ADALError: BROKER_AUTHENTICATOR_NOT_RESPONDING](https://github.com/AzureAD/azure-activedirectory-library-for-android/wiki/ADALError:-BROKER_AUTHENTICATOR_NOT_RESPONDING).
+    In certain devices and scenarios, you might experience sign-in failures when using an authenticator. This issue is due to the OEM limiting this functionality. For more information, see [ADALError: BROKER_AUTHENTICATOR_NOT_RESPONDING](https://github.com/AzureAD/azure-activedirectory-library-for-android/wiki/ADALError:-BROKER_AUTHENTICATOR_NOT_RESPONDING).
 
 1. **Office 365 Video connector isn't supported.**
 
-## Integration
+## Power Automate Integration
+
+1. **Power Automate flows are orphaned in Power Apps.**
+
+   Power Automate flows that are added using an older version of the Power Apps panel might be orphaned and removed. To fix this issue, readd the flows manually.
+
+1. **Power Apps custom pages (in a model-driven app) are out of synchronization with embedded Power Automate flow metadata.**
+
+    The metadata for a Power Automate flow might be out of synchronization with a model-driven app's custom page if the flow is updated after being embedded. To update, follow these steps for each embedded flow:
+
+    1. Edit the custom pages that use the flow.
+    2. Open the Power Automate pane and refresh the flow.
+    3. Save and republish the custom page.
 
-**Power Automate flows are orphaned in Power Apps.**
+    Once complete, follow these steps:
 
-Power Automate flows that are added using an older version of the Power Apps panel might be orphaned and removed. To fix this issue, readd the flows manually.
+    1. Edit the model-driven app.
+    2. Make a minor change to trigger the save option.
+    3. Save and publish the model-driven app.
 
 ## Power Fx
 
@@ -110,7 +130,7 @@ Power Automate flows that are added using an older version of the Power Apps pan
 
 **Performance degradation when opening Power Apps Studio in China**
 
-[Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) might take more than 30 seconds when loading in China. This issue doesn't impact tenants hosted locally by 21Vianet.
+[Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) might take more than 30 seconds when loading in China. This issue doesn't affect tenants hosted locally by 21Vianet.
 
 ## Studio and Forms
 
@@ -130,11 +150,11 @@ The [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) is home
 
 1. **Changing the layout of SharePoint forms**
 
-    While customizing SharePoint forms in certain languages, if you try to change the layout from **Portrait** (default) to **Landscape**, the app might show multiple errors (yellow triangles in controls). To resolve these errors and retain the landscape layout, select **Undo**.
+    When you customize SharePoint forms in certain languages, if you try to change the layout from **Portrait** (default) to **Landscape**, the app might show multiple errors (yellow triangles in controls). To resolve these errors and retain the landscape layout, select **Undo**.
 
 1. **Changing a flow in a shared app**
 
-    If you add a flow to an app, share it, and then add a service or change a connection in the flow, you must remove the flow from the shared app, readd the flow, and then reshare the app. Otherwise, users who trigger the flow receive an authentication failure.
+    If you add a flow to an app and share the app, and then make changes to the flow, such as adding a service or modifying a connection, more steps are required. You must also first remove the flow from the shared app. Next, readd the flow to the app. Finally, reshare the app.
 
 1. **Changing a "Title" field in a table**
 
@@ -146,7 +166,7 @@ The [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) is home
 
 1. **It can sometimes take a moment before a newly shared app can be used.**
 
-    In some cases, a newly shared app won't be immediately available. Wait a few moments, and it should become available.
+    In some cases, a newly shared app isn't immediately available. Wait a few moments, and it should become available.
 
 1. **In the [Form control](/power-apps/maker/canvas-apps/controls/control-form-detail), you can't change data by using a custom card.**
 

support/power-platform/power-apps/create-and-use-apps/isolate-common-issues.md

@@ -3,7 +3,7 @@ title: General Power Apps troubleshooting strategies
 description: Learn about general strategies to narrow down the cause of app errors.
 author: tahoon
 ms.reviewer: tapanm, lanced
-ms.date: 01/31/2025
+ms.date: 04/14/2025
 ms.author: tahoon
 ms.custom: sap:App Creation (Canvas App)
 search.audienceType: 
@@ -38,7 +38,7 @@ For model-driven apps:
 After you have isolated the issue to a specific functionality area, use the following sections to help you work around or address the issue.
 
 - [Connectors and delegation](common-issues-and-resolutions.md#connectors-and-delegation)
-- [Integration](common-issues-and-resolutions.md#integration)
+- [Integration](common-issues-and-resolutions.md#power-automate-integration)
 - [Power Fx](common-issues-and-resolutions.md#power-fx)
 - [Region](common-issues-and-resolutions.md#region)
 - [Studio and Forms](common-issues-and-resolutions.md#studio-and-forms)