Microsoft Power Platform Low-Code Services
View All Tags
Every control in a canvas app has a Visible property. Set it to a formula that's true or false, and the control appears or disappears as the formula changes. It's how you show a My team button only to managers, or a message only when something is missing.
An icon next to a button's text helps people find the right button at a glance. The modern Power Apps Button has an Icon property built in, so you don't need a separate icon control. Here's how to pick one, where to put it, and how to handle buttons that show only an icon.
Buttons are how people do things in a canvas app: open a screen, save a record, send a request. The modern Button control follows your app's theme and works with keyboards and screen readers out of the box. Here's how to add one and set it up.
The modern Avatar control shows a person as a round picture, or as their initials when there's no picture. Out of the box it shows the signed-in user, which makes it an easy way to personalise a home screen. It also ships with an Available presence badge you probably don't want. Here's how to add it and set it up properly.
The Text control is the modern way to show words on a canvas app screen: a heading, a message, or the result of a formula, such as the signed-in person's name. It's the modern replacement for the classic Label. Here's how to add one, fill it with a formula, and make it grow when the text is long.
Screen reader users often jump from heading to heading to understand a page. In a canvas app, text only counts as a heading if you mark it as one, and the only control that can do that is the classic Text label, through its Role property. Here's how to add one, even in an app built with modern controls.
A horizontal container lines up the controls inside it from left to right and spreads them across the space it has. Placed inside a vertical container, it's the natural way to build a header bar, a row of buttons, or a picture next to some text. Here's how to add one and give it a fixed height, using an app header as the example.
A vertical container stacks the controls inside it, top to bottom, and works out their positions for you. You never type an X or Y for them. Put one around a whole screen and set it to the screen's size, and everything inside follows when the window gets wider or narrower. It's the starting point of a responsive canvas app.
Good names make a canvas app readable: btnMyPlanHS tells you it's a button on the Home screen, Button4 tells you nothing. Microsoft publishes naming guidance for Power Apps, and following it costs nothing but a rename. Here it is in one place, with the Career Development Plan app as a worked example.
Every new screen and control gets a placeholder name: Screen1, Container1, Button1. Those names end up in your formulas, and screen names are read aloud by screen readers. Renaming takes a few seconds, and doing it as soon as you add something saves confusion later.
