Power Fx patterns that experienced makers use

Power Fx is designed to be approachable for makers who are not professional developers. It is also deep enough to reward practitioners who explore beyond the basics.

Named formulas: reuse without repetition

Named formulas in App.Formulas let you define a value or expression once and reference it everywhere. Instead of copying the same filter expression into twelve controls, define it once and reference the name. A change to the underlying data structure needs to be made in one place.

Context variables vs global variables

New makers reach for global variables (Set) for everything because they work anywhere. Experienced makers use context variables (UpdateContext) for screen-scoped state because they are more predictable and easier to debug. Use global variables only when you genuinely need to share state across screens.

Delegation: the performance boundary you must understand

Delegation determines whether a Power Fx expression is executed in the data source or in Power Apps. Non-delegable expressions retrieve the first 500 records and filter locally — silently returning incomplete results on large datasets. Know which functions are delegable for your connector.

Collections: when and how to use them

Collections are in-memory tables useful for staging data before submission and building multi-record selection UIs. They are not a substitute for a data source — do not use them to store data that needs to persist beyond the app session.

With() for readability

The With() function creates named aliases for complex sub-expressions within a formula. This makes long formulas significantly more readable by replacing repeated complex expressions with meaningful names.

The Power Fx patterns that matter most are the ones that make apps maintainable six months after they are built, by someone who was not there when they were built.