You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/power-apps/create-and-use-apps/common-issues-and-resolutions.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ contributors:
16
16
---
17
17
# Common issues and resolutions for Power Apps
18
18
19
-
This article lists common issues you might encounter while using Power Apps. We group issues by area and provide summary-level workarounds where applicable. Pointers to primary documentation locations are also provided.
19
+
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.
20
20
21
21
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.
22
22
@@ -62,11 +62,11 @@ End users might encounter this issue in two situations:
62
62
63
63
1.**Custom connectors and Microsoft Dataverse**
64
64
65
-
You need to make adjustments if you built your app with Power Apps:
65
+
You need to make adjustments if you built your app with Power Apps that:
66
66
67
-
1.Version 2.0.540 or earlier,
68
-
2. Relies on a Dataverse database,
69
-
3.And uses at least one custom connector from a separate environment.
67
+
1.Is version 2.0.540 or earlier.
68
+
2. Relies on a Dataverse database.
69
+
3.Uses at least one custom connector from a separate environment.
70
70
71
71
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).
72
72
@@ -102,7 +102,7 @@ End users might encounter this issue in two situations:
102
102
103
103
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.
104
104
105
-
1.**Power Apps custom pages (in a model-driven app) are out of synchronization with embedded Power Automate flow metadata**
105
+
1.**Power Apps custom pages (in a model-driven app) are out of synchronization with embedded Power Automate flow metadata.**
106
106
107
107
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:
108
108
@@ -154,7 +154,7 @@ The [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) is home
154
154
155
155
1.**Changing a flow in a shared app**
156
156
157
-
If you add a flow to an app and share the app, 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. And finally, reshare the app.
157
+
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.
0 commit comments