Low-Code and No-Code Development Platforms
View All Tags
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.
The app gets its home in this part: a Power Apps solution that holds the canvas app and three environment variables, which tell the app where its SharePoint data is. By the end, the app is created, connected to both lists and to Microsoft 365 user profiles, and ready for its first screen.
Where you create a canvas app matters. Create it from inside a solution and it belongs to that solution from the start: it can use the solution's environment variables, and it moves with the solution to other environments. This guide does exactly that, and takes a first look around Power Apps Studio.
A canvas app that reads a SharePoint list normally has the site's address and the list built into it. Move the app to another organization and it still points at the old site. Environment variables fix that: the app asks the variables where its data is, and each environment gives them its own values.
A solution is the box you build a Power Apps app in, so that the app and everything it needs can move to another environment together. Every solution belongs to a publisher, and the publisher's prefix ends up in the name of everything you create. Ten minutes spent on both now saves renaming later, which often isn't possible.
Every screen of the Career Development Plan app reads from or writes to two SharePoint lists. This part builds them, and the site they live on, column by column and setting by setting, exactly as the app will expect them.
Plenty of teams still track career development in spreadsheets: which skills each role needs, how far each person has got, and who has signed it off. This series replaces that with a Power Apps app. Each person sees the competencies their role expects and writes a short response for each one. Their manager then approves or declines it, all on SharePoint and the Microsoft 365 licenses you already have.
Power Apps keeps numbers the way a calculator does — 123456.789 — but the people using your app expect to read 123,456.79. The Text() function converts a number or integer to text and formats it in the same step, as long as you know the one situation where it silently does nothing.
