273 posts tagged with "Fixes"

You set a label in a gallery to a SharePoint column, and instead of text you get a red error icon and Expected Text value. The column is a Choice column, and Power Apps gets a Choice as a record, not as text. Add .Value and it works.

You open your app in Power Apps Studio and nothing can be changed. The title says (Read-only), the formula bar says Cannot edit in read-only editor, and a banner explains: This app is read-only because you already have editing control elsewhere. Nobody else is editing; "elsewhere" is another session of yours. Override gets you editing again.

The App checker in Power Apps Studio lists red errors: Missing accessible label, one per control. Your screen looks fine, but people using a screen reader get nothing useful from those controls. The fix is to give each one an AccessibleLabel that says what it is or what it does.

The screen looks perfect on your monitor. Then you preview it on a phone, and the text is cut off: half of a heading disappears under the header, and a sentence ends mid-way. Auto height is on, so the text controls are growing. The problem is the container around them, which has a fixed height and doesn't.

The modern Avatar control is supposed to show a person's initials when they have no photo. With its default settings, for a user without a photo, it showed a grey person silhouette instead. The cause is User().Image, which returns a default picture rather than nothing. One check with Office 365 Users brings the initials back.

Your canvas app calls Office365Users.ManagerV2 and a red banner appears: Office365Users.ManagerV2 failed … Resource 'manager' does not exist or one of its queried reference-property objects are not present. Nothing is broken in your formula. The person simply has no manager in Microsoft 365, and ManagerV2 reports that as an error rather than a blank.

You type a formula with Set, Navigate or Patch into a property, and Power Apps underlines it in red: Behavior function in a non-behavior property. The formula isn't wrong as such; it's in the wrong place. Functions that do something can only run when something happens, such as a button being selected.

You open a SharePoint list environment variable in your Power Apps solution to change something small, such as its display name, and the panel starts with a red error: We are unable to find the list. Site is empty, the list isn't shown, and Save is disabled. The variable still works. The edit panel just needs you to choose the site and list again.

You're creating a SharePoint environment variable in a Power Apps solution, you've typed its name, and you have no SharePoint connection yet. You choose + New connection, and Power Apps asks Are you sure you want to discard changes? Discarding throws your form away, and no connection page opens. The fix is to do things in a different order.

You open a solution in Power Apps and a yellow bar across the top says One or more commands are unavailable due to your current privileges for this environment. Nothing is broken. Your Dataverse security role simply doesn't allow some of the solution's commands, so Power Apps hides or disables them.