The Power Apps Choices function reads the allowed values of a SharePoint choice or lookup column, so your drop down always matches the list. Put it in a control’s Items property and you never type the options by hand:
Choices([@'Service Requests'].Status)
On my 620-item Service Requests list, that one line returned a three-row table: New, In Progress and Closed.
In this tutorial, we’ll use the Power Apps Choices function in a drop down, a combo box, a gallery filter and an edit form. We’ll also cover the text filter, delegation and the error you get on a text column.
Build the Demo App Step by Step
New to canvas apps? Here’s the exact app I tested in, so you can follow along. Our Power Apps tutorials hub covers every control in more depth.
1. Check the list. A data source is where the app reads its records. Mine is the SharePoint list Service Requests on the SPGuides site, with two choice columns, Status and Priority:

Open a column’s settings and you’ll see its choices. Status allows New, In Progress and Closed, with New as the default. Priority allows Low, Normal and High:

2. Open the maker portal. Go to make.powerapps.com, stay on Home and select Start with design:

3. Start a blank canvas app. On the Create an app page, select Create from blank:

4. Pick a layout. In Start with a blank canvas, choose Tablet. Power Apps Studio, the app editor, opens:

5. Add the data. Select Add data on the command bar, type SharePoint in the search box and pick the SharePoint connector:

6. Connect to the site. Paste the site URL into Connect to a SharePoint site and select Connect:

7. Choose the list. Search for Service, check Service Requests and select Connect:

8. Insert a control. Open Insert, type drop in the search box and select Drop down. The same search finds the Combo box, Gallery and Edit form:

To give a control a formula, select it, pick the property (such as Items) in the dropdown left of the fx formula bar, then type in the bar.
To test, select Play (the preview button, top right), or hold Alt and click a control in the editor. Press Ctrl+S to save. You don’t need to publish just to test.
Power Apps Choices() Syntax
Here’s the full signature from Microsoft’s Power Fx reference:
Choices( column-reference [, text-filter ] )
| Argument | Required | What it does |
|---|---|---|
| column-reference | Yes | A choice or lookup column, written directly against the data source, like [@'Service Requests'].Status. No quotes. |
| text-filter | No | Returns only the choices that start with this text. An empty string returns all of them. |
The result is a table. For a SharePoint choice column, each row has a Value field holding the text, which is why you’ll see .Value everywhere below.
The reference can’t go through a variable, a function or a control. Write the list and column name every time.
Only need the value stored on one item? Read it with ThisItem.Status.Value, as shown in our guide to get a choice field value in Power Apps.
The [@'Service Requests'] part is the disambiguation operator. It tells Power Apps you mean the data source, not a control or variable with a similar name.
How Do You Use Choices in a Power Apps Drop Down?
I named my drop down ddStatus and set its Items property to the Status column. If the control is new to you, start with our Power Apps drop down control guide:

Choices([@'Service Requests'].Status)
In Preview, the list showed New, In Progress and Closed, in the same order as the SharePoint column settings:

To read the pick as text, use ddStatus.Selected.Value. My label showed In Progress after I picked In Progress.
To open on a specific choice, set the drop down’s Default property to that text. My Default is "Closed", and the app started on Closed. For more patterns, see how to set a drop down default value from a SharePoint list.
Need the pick on another screen? Store ddStatus.Selected.Value in a global variable with Set. Our post on global vs context variables in Power Apps explains which one to use.
Choices in a Combo Box: Items, Default and Multi-Select
A combo box takes the same Items formula, but it adds search and multi-select. Our Power Apps combo box control tutorial covers the rest of its properties. My cbPriority box uses the Priority column:

// Items
Choices([@'Service Requests'].Priority)
// DisplayFields
["Value"]
// DefaultSelectedItems
[{Value: "High"}]
Use DefaultSelectedItems for the starting pick. Microsoft lists the old Default property as deprecated. With the record above, the box opened with High selected.
Multi-select is on by default. In Preview, I added Low next to High:

A label with Concat(cbPriority.SelectedItems, Value, ", ") then showed High, Low. Want one pick only? Set SelectMultiple to false. If you need to clear the box later, here’s how to reset a Power Apps combo box.
How Many Choices Are There? CountRows and the Text Filter
Because Choices returns a table, every table function works on it. I tested three on the same screen, and the Concat function for joining text turns the table into one line:
CountRows(Choices([@'Service Requests'].Status)) // 3
Concat(Choices([@'Service Requests'].Priority), Value, ", ") // Low, Normal, High
Concat(Choices([@'Service Requests'].Status, "In"), Value, ", ") // In Progress

The text filter is a starts-with match. “In” kept In Progress and dropped New and Closed. It’s handy for type-ahead lists on columns with many choices.
Need the options in a different order? Because the result is a table, you can wrap it in Sort. Our post on how to sort drop down choices alphabetically walks through it.
Filter a Gallery by the Selected Choice
This is the most common real use: pick a status, see the matching requests. Our filter a Power Apps gallery by drop down post has more variations. My gallery’s Items property:
SortByColumns(
Filter('Service Requests', Status.Value = ddStatus.Selected.Value),
"ID", SortOrder.Descending
)

Studio showed no delegation warning on this gallery. A delegation warning is the yellow triangle Power Apps shows when a formula can’t be sent to SharePoint and only the first 500 rows are checked.
The results prove it delegated. With In Progress picked, the first row was ID 620, the last item in the list:

Closed started at ID 618 and New at ID 619, all past row 500. SortByColumns delegates here too; our Power Apps Sort and SortByColumns guide lists the rules.
Is the Choices Function Delegable?
No. Microsoft’s reference says Choices can’t be delegated at this time. For a choice column, that rarely matters, because the function returns the column’s options, not your list items. Three options load instantly.
It matters for lookup columns. Choices on a lookup returns rows from the other list, so a big lookup list gets cut at the data row limit. The fix is to add that list as its own data source and filter it directly.
The counting formula is where I hit a warning. This label counts the matching items:
CountRows(Filter('Service Requests', Status.Value = ddStatus.Selected.Value))

The tooltip says the CountRows operation isn’t supported by this connector. The counts were still right: 206 Closed, 207 In Progress and 207 New, which adds up to 620.
That holds only while the filtered result stays under the data row limit. Our Power Apps delegation guide and the Power Apps CountRows function post explain when counts go wrong.
Choices in an Edit Form Choice Field
You don’t always need to write Choices yourself. When I inserted an Edit form and set its data source to Service Requests, Power Apps built the Status card on its own.
Our post on how to submit a Power Apps form to a SharePoint list builds the full form.
Select the combo box inside the Status card. Its Items property already holds the formula:

Choices([@'Service Requests'].'Status')
The breadcrumb at the bottom shows the path: Form1, then Status_DataCard1, then DataCardValue2. To limit the options, edit this Items formula, for example with Filter, rather than changing the SharePoint column.
If a card shows an error after you change a column in SharePoint, refresh the data source in the Data pane so the app picks up the new choices.
Common Choices Errors and Fixes
The function ‘Choices’ has some invalid arguments
Requester in my list is a plain text column. Pointing Choices at it fails before the app even runs:
CountRows(Choices([@'Service Requests'].Requester))

Choices only works on choice and lookup columns. For a text column, build the list from the data instead with Distinct, as in show only unique values in a drop down.
Forgetting .Value
A choice value is a record, not text, so a label can’t show it directly. Use ddStatus.Selected.Value or ThisItem.Status.Value wherever you need the words.
Choices doesn’t accept a variable or control
Microsoft’s rule is strict: the reference can’t pass through a gallery, a variable or a function, so galRequests.Selected.Status won’t work inside Choices. Point it at the data source, such as [@'Service Requests'].Status.
If you build apps like this every week, our Power Apps training course covers choice columns, forms and delegation on real projects.
A few more Power Apps posts that build on choice columns:
Frequently Asked Questions
What does the Choices function do in Power Apps?
It returns a table of the allowed values for a choice or lookup column, such as New, In Progress and Closed. You usually put it in the Items property of a drop down, combo box or radio control.
How do I get choices from a SharePoint list in Power Apps?
Connect the list as a data source, then set a control’s Items property to Choices([@’Your List’].YourColumn). Read the picked text with Selected.Value on a drop down or SelectedItems on a combo box.
Is the Power Apps Choices function delegable?
No. Choices can’t be delegated. That’s fine for choice columns, which have a handful of options, but for large lookup lists add the other list as a data source and filter it directly.
Why does Choices give an invalid arguments error?
The column isn’t a choice or lookup column, or the reference goes through a variable or control. Point it straight at a choice column on the data source.
Where is the Choices function documented?
Microsoft documents the syntax, the optional text filter and the delegation limit in the Choices function reference on Microsoft Learn.

Hey! I’m Bijay Kumar, founder of SPGuides.com and a Microsoft Business Applications MVP (Power Automate, Power Apps). I launched this site in 2020 because I truly enjoy working with SharePoint, Power Platform, and SharePoint Framework (SPFx), and wanted to share that passion through step-by-step tutorials, guides, and training videos. My mission is to help you learn these technologies so you can utilize SharePoint, enhance productivity, and potentially build business solutions along the way.
Amazing article however it missing one important thing:
How to filter choices in one dropdown based on the value of the second dropdown.
I.e. There 2 columns “Building” and “Floor”. Each building has different floors but Sharepoint list column “Floor” declared as Choices contains all type of floors.
So the Buiding dropdown has an obvious code: Items = Choices(Table.Building) so how to code the Floor dropdown?