Fixes for Common Issues and Errors
View All Tags
Incompatible types for comparison. These types can't be compared: Number, Error. means one side of a comparison has already failed. In my case, a duplicated screen compared a number with a context variable that only the original screen receives. The fix is to give the new screen its own variable.
A manager approved an employee's response, but the employee's screen kept saying Waiting for review, even after she opened it again. Microsoft documents why: a running canvas app doesn't pick up changes other people make. The fix is to call Refresh when a screen opens, and to give people a Refresh button for when they stay on a screen.
In Power Apps Studio, copying a control puts its code on the clipboard, and pasting creates a control from that code. If you copy anything else in between, such as a formula, the paste fails with There's something wrong with the pasted code. Check the code and try again. The fix is to copy the control again right before you paste it.
The '.' operator cannot be used on Error values means the name on the left of a dot has already failed, so Power Apps can't read a field from it. In my case, a copied control brought along a context variable that only exists on another screen. The fix is on the left of the dot.
You publish a new version of a canvas app, and a user who has it open still sees the old one. In the example, no update notice appeared, and even the first reload, a few minutes later, still opened the previous version. Reloading again a few minutes after that loaded the new screens.
Power Apps Studio attaches this note to an app's data sources: A Power Apps per user plan, Power Apps per app plan or Power Apps pay-as-you-go plan will be required during playback for apps with this connector. In the example, it was attached to SharePoint and Office 365 Users, which are standard connectors. The app's License designation said Standard, and a user with only a Microsoft 365 license ran it.
Counting SharePoint items with CountRows(Filter(...)) puts a yellow triangle on the screen: Delegation warning. The highlighted part of this formula might not work correctly on large data sets. The "CountRows" operation is not supported by this connector. SharePoint can't count, so the count happens in the app, on at most 500 items. The fix is to ask SharePoint a question it can answer.
A label's formula uses a variable, and Power Apps underlines it in red: Name isn't valid. 'locMember' isn't recognized. The name is spelled correctly. The variable simply doesn't exist yet, because nothing in the app creates it.
A screen loads a saved record into a text input, yet when the screen opens again, the box shows text that was never saved. A text input keeps whatever was typed until its Default changes. If the saved value is the same as last time, nothing resets it. Reset in the screen's OnVisible fixes it.
Patch fails with Network error when using Patch function: [YourList] ETAG mismatch. It isn't a network problem. The SharePoint item changed after your app read it, so SharePoint refused to overwrite the newer version. Catch it with IfError, tell the person what happened, and reload the item.
