Standards

Power Apps Naming Standards

Naming guidance for screens, controls, variables, collections, components, and formulas in maintainable canvas apps.

Power Apps naming standardscanvas app standardsPower Fx variables

Who this helps

Teams building apps that more than one maker will maintain.

What to standardize

Use predictable prefixes for controls and variables.
Name screens around user tasks.
Avoid abbreviations only one maker understands.
Document exceptions in app notes.

Examples

Recommended prefixes

Keep formulas readable across screens.

Formula / code

Screens: scrRequestList, scrRequestDetail
Galleries: galRequests, galApprovers
Forms: frmRequest
Inputs: txtTitle, cmbPriority, dpDueDate
Variables: varSaving, varCurrentRequest
Collections: colReviewQueue, colSelectedApprovers

Expected result: A new maker can infer purpose before opening every control property.

Common mistakes

Leaving default names like Button12
Using different prefixes per maker
Encoding business rules into cryptic names