If you’re still typing string values like "Primary", "Center", or "Bold" into your Power Apps formulas, you’re working with “technical debt” by design.
With the latest ** 2026 Modern Control updates**, Power Apps has officially shifted toward Typed Enums. This isn’t just a UI change, it’s a fundamental shift toward robust app architecture.
The Problem with “Loose Strings”
In classic Power Apps, we used patterns like:
Button1.Appearance = "Primary"
As an architect, here is why this is brittle:
- ❌ No Design-Time Validation: Typos don’t fail until the app runs (or fails silently).
- ❌ Zero Discoverability: You have to memorize or look up valid string values.
- ❌ Maintenance Nightmare: If Microsoft updates a property name, your strings become “magic text” that is hard to find and replace.
Enter: Typed Enums
Modern controls (Button, Tab List, Combo Box, etc.) now enforce Typed Enum Values. Instead of a string, you reference a predefined object:
Button1.Appearance = Appearance.FilledButton.Appearance.Filled
Note: enum names are control‑specific
Why this is a “Pro” Move:
- Intellisense-Driven: The moment you type the “dot” (
.), Power Apps shows you exactly what is valid. - Type Safety: The Power Fx engine validates the formula instantly. If it’s not in the Enum, it’s an error.
- Cleaner Logic: It aligns Power Apps with professional languages like TypeScript and C#.
This shift enables safer upgrades, better tooling, and predictable breaking-change detection.
Classic vs. Modern: The Comparison
| Feature | Classic (String-Based) | Modern (Typed Enum) |
|---|---|---|
| Formula | Align = "Center" | Align = Align.Center |
| Validation | None (Loose) | Strict (Strongly Typed) |
| Speed | Manual typing | Intellisense Selection |
| Reliability | High risk of typos | Errors are caught immediately at design time |
Common Enums You Should Use Now
As of the 2026 release, look for these patterns in your Modern Controls:
- Button/Tab List:
Appearance.Filled,Appearance.Subtle,Appearance.Outline - Text/Input:
Align.Center,FontWeight.Semibold - Validation:
ValidationState.Error,ValidationState.None
Migration Tip:
If IntelliSense doesn’t show enum values, you’re likely using a classic control. Replace it with a modern equivalent to unlock typed enums.
Final Takeaway
If you want to build enterprise-grade apps that don’t break, stop using quotes. Embrace the dot. Using Typed Enums is the fastest way to improve your app’s architecture without changing a single line of business logic.
Watch the 60-second breakdown here: Stop using Strings in Power Apps Modern Controls
Found this helpful? I’d appreciate it if you could share this with your team or mark this as a helpful resource in the Power Platform community!
Let’s Connect
How is your organization handling the shift to Managed Environments in 2026? I would love to hear your thoughts in the Power Platform Community or on LinkedIn.
Sunil Kumar Pashikanti
Principal Software Architect & Microsoft Community Super User. With 18+ years in the Microsoft ecosystem, I specialize in bridging the gap between enterprise business needs and advanced technical execution across Power Platform and Azure.