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
+39-21Lines changed: 39 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ For a description of how to monitor the data being sent and returned, see [Debug
54
54
55
55
For more information about how to share an app for SharePoint, see [Connect to SharePoint from a canvas app](/power-apps/maker/canvas-apps/connections/connection-sharepoint-online).
56
56
57
-
-**SQL data sources no longer add a "[dbo]" prefix to the data source name.**
57
+
-**SQL data sources no longer add a `[dbo]` prefix to the data source name.**
58
58
59
59
For more information about this change, see [Connect to SQL Server from Power Apps](/power-apps/maker/canvas-apps/connections/connection-azure-sqldatabase).
60
60
@@ -70,11 +70,13 @@ For a description of how to monitor the data being sent and returned, see [Debug
70
70
71
71
-**Column names with spaces**
72
72
73
-
If you're using a list created using Microsoft Lists, a SharePoint library, or an Excel table in which a column name contains a space, use single quotes with the column name, like this`someList.'Color Tag'`.
73
+
If you're using a list created using Microsoft Lists, a SharePoint library, or an Excel table in which a column name contains a space, use single quotes with the column name, for example`someList.'Color Tag'`.
74
74
75
75
-**Apps that connect to on-premises SharePoint**
76
76
77
-
If you share an app that relies on connections that aren't automatically shared (for example, an on-premises SharePoint site), users who open the app in a browser see a dialog box with no text when they select or tap **Sign in**. To close the dialog box, select or tap the close (X) icon in the upper-right corner. The dialog box doesn't appear if you open the app in [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) or [Power Apps mobile](/power-apps/mobile/run-powerapps-on-mobile). For more information about shared connections, see [Share app resources](/power-apps/maker/canvas-apps/share-app-resources).
77
+
If you share an app that relies on connections that aren't automatically shared (for example, an on-premises SharePoint site), users who open the app in a browser see a dialog box with no text when they select or tap **Sign in**. To close the dialog box, select or tap the close (X) icon in the upper-right corner.
78
+
79
+
The dialog box doesn't appear if you open the app in [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) or [Power Apps mobile](/power-apps/mobile/run-powerapps-on-mobile). For more information about shared connections, see [Share app resources](/power-apps/maker/canvas-apps/share-app-resources).
78
80
79
81
-**For apps that are created from data, only the first 500 records of a data source can be accessed.**
80
82
@@ -90,19 +92,19 @@ For a description of how to monitor the data being sent and returned, see [Debug
90
92
91
93
-**Sign-in issues on certain Android mobile devices when using authenticator**
92
94
93
-
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).
95
+
In certain devices and scenarios, you might experience sign-in failures when using an authenticator. This issue is due to limitation imposed by the OEM. For more information, see [ADALError: BROKER_AUTHENTICATOR_NOT_RESPONDING](https://github.com/AzureAD/azure-activedirectory-library-for-android/wiki/ADALError:-BROKER_AUTHENTICATOR_NOT_RESPONDING).
94
96
95
97
-**Office 365 Video connector isn't supported.**
96
98
97
99
## Power Automate integration
98
100
99
101
-**Power Automate flows are orphaned in Power Apps.**
100
102
101
-
Power Automate flows that are added using an older version of the Power Apps panel might become orphaned and removed. To fix this issue, readd the flows manually.
103
+
Power Automate flows that are added using an older version of the Power Apps panel might become orphaned and removed. To fix this issue, re-add the flows manually.
102
104
103
105
-**Power Apps custom pages (in a model-driven app) are out of synchronization with embedded Power Automate flow metadata.**
104
106
105
-
The metadata for a Power Automate flow might get out of synchronization with a model-driven app's custom page if you update the flow after embedding it. To update the metadata, follow these steps for each embedded flow:
107
+
The metadata for a Power Automate flow might get out of synchronization with a model-driven app's custom page, if you update the flow after embedding it. To update the metadata, follow these steps for each embedded flow:
106
108
107
109
1. Edit the custom pages that use the flow.
108
110
1. Open the Power Automate pane and refresh the flow.
@@ -120,14 +122,14 @@ For more information about Power Fx, see [Microsoft Power Fx](/power-platform/po
120
122
121
123
-**`Connection.Connected` returns the wrong value during OnStart in Power Apps for Windows.**
122
124
123
-
While offline, the **[Connection.Connected](/power-platform/power-fx/reference/signals#connection)** formula might wrongly return **true** immediately after starting an app in the Windows app. As a workaround, use a **Timer** control to delay the execution of the logic depending on it.
125
+
While offline, the **[Connection.Connected](/power-platform/power-fx/reference/signals#connection)** formula might wrongly return **true** immediately after starting an app in Power Apps for Windows. As a workaround, use a [Timer](/power-apps/maker/canvas-apps/controls/control-timer) control to delay the execution of the logic depending on it.
124
126
125
127
-**Issues with Date-time**
126
128
127
129
For more information about date and time issues, see:
128
130
129
-
-[Troubleshoot Canvas app date time issues](troubleshoot-canvas-app-date-time-issues.md)
130
-
-[Troubleshoot Model driven app date time issues](troubleshoot-model-driven-app-date-time-issues.md)
131
+
-[Troubleshoot Canvas app date time issues](./troubleshoot-canvas-app-date-time-issues.md)
132
+
-[Troubleshoot Model driven app date time issues](./troubleshoot-model-driven-app-date-time-issues.md)
131
133
132
134
## Regional performance
133
135
@@ -141,27 +143,43 @@ The [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) hosts t
141
143
142
144
-**Problems with startup**
143
145
144
-
If you have trouble accessing or starting Power Apps, see [troubleshooting startup issues](~/power-platform/power-apps/sign-in/troubleshooting-startup-issues.md).
146
+
If you have trouble accessing or starting Power Apps, see [Troubleshooting startup or sign-in issues for Power Apps](~/power-platform/power-apps/sign-in/troubleshooting-startup-issues.md).
145
147
146
148
-**Problems changing dimensions or orientation of SharePoint forms**
147
149
148
-
If you have issues with the **Screen size + orientation** settings for custom SharePoint forms, you can use the **Custom** size to work around the issue. First, reset the setting by selecting the **Small** size, then toggle **Orientation** to **Portrait** and then back to **Landscape**. Then, select **Custom** and enter a desired screen size. For reference, the preset values are "Width: 270, Height: 480" for the Small Portrait size, and "Width: 720, Height: 480" for the Small Landscape size.
150
+
If you have issues with the **Screen size + orientation** settings for custom SharePoint forms, you can use the **Custom** size to work around the issue:
151
+
152
+
1. Reset the setting by selecting the **Small** size,
153
+
1. Toggle **Orientation** to **Portrait** and then back to **Landscape**.
154
+
1. Select **Custom** and enter a desired screen size. For reference, the preset values are:
155
+
- "Width: 270, Height: 480" for the Small Portrait size.
156
+
- "Width: 720, Height: 480" for the Small Landscape size.
149
157
150
158
-**Copying and pasting screens across apps**
151
159
152
-
Copying and pasting screens across apps isn't currently supported. To work around this issue, add a new screen to your target app, copy the controls from the screen in your source app, and then paste them into the screen of your target app.
160
+
Copying and pasting screens across apps isn't currently supported. To work around this issue:
161
+
162
+
1. Add a new screen to your target app.
163
+
1. Copy the controls from the screen in your source app.
164
+
1. Paste the controls into the screen of your target app.
153
165
154
166
-**Changing the layout of SharePoint forms**
155
167
156
168
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**.
157
169
158
170
-**Changing a flow in a shared app**
159
171
160
-
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.
172
+
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, re-add the flow to the app. Finally, re-share the app.
161
173
162
174
-**Changing a "Title" field in a table**
163
175
164
-
If you change the **Title** field for a table that other tables reference through one or more lookups, an error occurs when you try to save the change. To work around this issue, remove any lookups to the table for which you want to change the **Title** field, make the change, and then re-create the lookups. For more information about lookups, see [Create a relationship between tables](/power-apps/maker/data-platform/data-platform-entity-lookup).
176
+
If you change the **Title** field for a table that other tables reference through one or more lookups, an error occurs when you try to save the change. To work around this issue:
177
+
178
+
1. Remove any lookups to the table you want to change.
179
+
1. Change the table's **Title** field.
180
+
1. Re-create the lookups.
181
+
182
+
For more information about lookups, see [Create a relationship between tables](/power-apps/maker/data-platform/data-platform-entity-lookup).
165
183
166
184
-**When Power Apps generates an app from data, the field used for sorting and searching isn't automatically configured.**
167
185
@@ -173,15 +191,15 @@ The [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) hosts t
173
191
174
192
-**In the [Form control](/power-apps/maker/canvas-apps/controls/control-form-detail), you can't change data by using a custom card.**
175
193
176
-
The stock custom card is missing the **[Update](/power-apps/maker/canvas-apps/controls/control-card)** property, which is required to write back changes. To work around this issue:
194
+
The stock custom card is missing the [Update](/power-apps/maker/canvas-apps/controls/control-card) property, which is required to write back changes. To work around this issue:
177
195
178
-
- Select the **Form** control, and insert a card by using the right-hand pane based on the field that you want the card to show.
179
-
- Unlock the card, as described in [Understanding data cards](/power-apps/maker/canvas-apps/working-with-cards#unlock-a-card).
180
-
- Remove or rearrange controls within the card as you see fit, just as you would with the custom card.
196
+
1. Select the **Form** control, and insert a card by using the right-hand pane based on the field that you want the card to show.
197
+
1. Unlock the card, as described in [Understanding data cards](/power-apps/maker/canvas-apps/working-with-cards#unlock-a-card).
198
+
1. Remove or rearrange controls within the card as you see fit, just as you would with the custom card.
181
199
182
200
-**Card gallery is deprecated.**
183
201
184
-
Existing apps that use this feature continue to run for now, but you can't add a card gallery. Replace card galleries with the new **[Edit form](/power-apps/maker/canvas-apps/controls/control-form-detail)** and **[Display form](/power-apps/maker/canvas-apps/controls/control-form-detail)** controls.
202
+
Existing apps that use this feature continue to run for now, but you can't add a card gallery. Replace card galleries with the new [Edit form](/power-apps/maker/canvas-apps/controls/control-form-detail) and [Display form](/power-apps/maker/canvas-apps/controls/control-form-detail) controls.
185
203
186
204
## Browser performance
187
205
@@ -199,9 +217,9 @@ The [Power Apps Studio](/power-apps/maker/canvas-apps/power-apps-studio) hosts t
199
217
200
218
When this issue occurs, consider using a web player on the Windows platform.
201
219
202
-
-**Microsoft Entra Conditional Access with the policy "Require device to be marked as compliant" doesn't work in Power Apps for Windows.**
220
+
-**Microsoft Entra Conditional Access with the policy _Require device to be marked as compliant_ doesn't work in Power Apps for Windows.**
203
221
204
-
When the Conditional Access policy is set to "Require device to be marked as compliant" in Microsoft Entra ID, users receive the following sign-in error and can't access their Power Apps.
222
+
When the Conditional Access policy is set to _Require device to be marked as compliant_ in Microsoft Entra ID, users receive the following sign-in error and can't access their Power Apps.
205
223
206
224
> The application contains sensitive information and can only be accessed from devices or client applications that meet your enterprise management compliance policy.
0 commit comments