Power Apps Naming Conventions
Establish consistent naming conventions in Power Apps for screens, controls, formulas, functions and variables to improve app development efficiency.
In Canvas Power Apps, renaming screens and controls for easier reference and maintenance during app development enhances overall efficiency.
Screen Names
Screen names should include the word “Screen” so screen readers can convey the information to the user, and they should be human-friendly.
Example |
|---|
Home Screen |
Print Screen |
Order List Screen |
Order Form Screen |
Controls
Control names should include the control type and a shortened parent screen name for easy identification when writing formulas.
Control | Prefix |
|---|---|
Add Picture | pic |
Address Input | add |
Button | btn |
Camera | cam |
Chart | chr |
Check Box | chk |
Collection | col |
Container | con |
Combo Box | cmb |
Component | cmp |
Date Picker | dte |
Drop Down | drp |
Form | frm |
Gallery | gal |
Group | grp |
HTML | htm |
Icon | ico |
Image | img |
Label | lbl |
Map | map |
PDF Viewer | |
Radio | rad |
Rich Text Editor | rte |
Slider | sld |
Table | tble |
Text Input | txt |
Timber | tmr |
Toggle | tgl |
Video | vid |
Here are examples.
Example | Description |
|---|---|
lbl_OrderForm_Name | A label for the "Name" field on the "Order Form" |
txt_OrderForm_Name | A Text Input control for the "Name" field on the "Order Form" |
cmb_OrderForm_Department | A ComboBox control for the "Department" field on the "Order Form" |
drp_OrderForm_Location | A Dropdown control for the "Location" field on the "Order Form" |
btn_OrderForm_Save | A Button control that saves the Order Form |
con_OrderForm_Outer | A container that represents the outermost container on the Order Form. |
dte_OrderForm_OrderDate | A Date Picker for the "Order Date" field on the "Order Form." |
gal_Orders_Orders | A Gallery control with "Orders" on the "Orders" screen. |
rad_OrderForm_Status | A Radio Button control for the "Status" field on the "Order Form." |
sld_OrderForm_Priority | A Slider control for the "Priority" field on the "Order Form." |
tgl_OrderForm_IsActive | A Toggle control for the "Is Active" field on the "Order Form." |
Named Formulas
Named Formulas in your app provide a unique way to calculate values for your app. They are similar to variables, but instead of storing the value in memory, the formula is triggered each time it’s accessed.
No spaces or underscores needed.
Example | Description |
|---|---|
fxCurrentUserEmail | A formula that displays the current user’s name. |
fxCurrentUserIsAdmin | A boolean named formula that indicates if the current user is an admin. |
User Defined Functions
A new Power Apps feature, User Defined Functions, lets you create functions that take inputs, execute a formula, and return an output. It is an effective way to make code reusable in Power Apps.
Example | Description |
|---|---|
udCalculateDate | A user-defined function that calculates a date. |
udSaveProduct | A user-defined function that saves a product to a collection. |
Variables
The app needs good names for its variables. There are two types: Global and Local. A Global variable is created using the Set function and can be accessed across multiple screens, while a Local variable is created using the UpdateContext function and can only be accessed on the current screen.
Prefix each variable with its type (Global or Local) and data type (Record, Text, Number, Date, etc.).
No spaces or underscores needed.
Example | Description |
|---|---|
varRecordSelectedOrder | A global variable containing the selected order used across various screens. |
tmpNumSelectedOrderId | A local variable stores the selected Order ID displayed on the screen. |
Collections
Collections should be accessible across the app and include the data source in the name. No spaces or underscores are needed.
Example | Description |
|---|---|
colSpOrders | A SharePoint list of Orders. |
colSqlEmployees | A SQL Table of Employees. |
colDVCustomers | A Dataverse collection of Customers. |
Data Sources
Your Data Sources should also have human-readable names that are easy to identify the type of data it holds. Our Data Source names are created when we connect to the Data Source, which means we don't have specific control to change it within the Power App.
Example | Description |
|---|---|
Orders | |
Employees | |
Inspections |