Microsoft Power Platform Low-Code Services
View All Tags
Power Apps Studio has a setting called Enable App.OnStart property, with a warning that OnStart "can cause delays when loading an app". It's tempting to switch it off to keep an app fast. This guide tested what the switch actually changes, and the result is a little surprising: in Studio, an OnStart formula still ran with the switch off.
Modern controls follow your app's theme on their own. Containers and classic controls don't: their colors and fonts stay whatever you set. The fix is to point those properties at the theme itself with App.Theme, so a header bar or a title label changes along with everything else when you switch themes.
A modern theme sets the colors and font of every modern control in a canvas app at once. Pick a theme, and buttons, avatars and anything else that follows the theme change together. Here's where the themes are, what happens when you pick one, and how to answer the question Studio asks about classic controls.
Modern controls are the newer set of Power Apps controls, built on Microsoft's Fluent 2 design system. They look current, work better with screen readers and keyboards, and all take their colors from one theme. In some apps they're switched off, and the Insert pane only offers the older, classic controls. Here's how to turn them on.
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.
