Understanding the Big Three: Screens, Controls, and Properties
Imagine you are building a house. You need rooms to walk through, furniture to use, and specific details like the color of the walls or whether a door is locked.
In PowerApps, those translate directly to Screens, Controls, and Properties. Every app, from a simple vacation request tool to a complex inventory system, is just a combination of these three things.
1. Screens: The “Rooms” of Your App
Screens are the containers for everything else. They define the boundaries of what a user sees at any given time.
Pro Tip: Give your screens meaningful names! Instead of the default Screen1, name it scr_Dashboard or scr_UserEntry. It makes your life much easier when you start writing navigation formulas like Maps(scr_Dashboard).
How they work: Most apps start with a “Browse” screen, move to a “Detail” screen, and end on an “Edit” screen.
2. Controls: The “Furniture”
Controls are the interactive elements you drop onto a screen. If a user can see it, click it, or type into it, it’s a control.
Common controls include:
- Labels: To display text or instructions.
- Buttons: To trigger actions (like saving data).
- Galleries: To show a list of items (like a list of customers).
- Forms: To collect data from the user.
- Text Inputs: Where users type in their information.
3. Properties: The “Logic and Style”
This is where the magic happens. Every Control has a list of Properties that determine how it looks and behaves. You find these in the dropdown menu on the top left of the formula bar.
| Property | What it controls | Example |
|---|---|---|
| Text | What words are displayed. | "Submit Application" |
| Fill | The background color. | Color.Blue or ColorValue("#0078d4") |
| OnSelect | What happens when clicked. | SubmitForm(Form1) |
| Visible | Whether the user can see it. | varShowButton (True/False) |
| Default | The starting value of a field. | User().FullName |
How They Work Together: An Example
Think about a “Submit” button on a “Success” screen:
- The Screen holds the button.
- The Control is the Button itself.
- The Properties are:
Text: “All Done!”DisplayMode: Disabled until the user fills in all fields.OnSelect:Maps(scr_Home)
Master the Canvas
Understanding these three pillars is the difference between feeling lost in the Studio and feeling like an architect. Everything you do from here on out—from variables to Dataverse integrations—will just be different ways of manipulating Properties on Controls across various Screens.