Live training: next batches coming soon. Join the waitlist:Waitlists open:Developer Training →Developer →Copilot Studio Training →Copilot Studio →

Power Apps Dropdown Control: Add Items, Get the Selected Value and Set a Default

If you’ve tried binding a Power Apps dropdown to a SharePoint list, you’ve probably seen it open with blank rows. Point Items at the list, then name the column to show: ItemDisplayText on the modern dropdown, Value on the classic one.

It happens because a list gives the control whole records, not text. The control still has to be told which column belongs on screen, and the modern and classic versions handle that differently.

In this tutorial, we’ll use the Power Apps dropdown with typed values, a SharePoint text column and a Choice column. Then we’ll read the selected value, set a default, and test what really happens past 500 rows.

The Sample List We’ll Use

Everything below uses one SharePoint list, Service Requests. It has a Title text column plus Status and Priority Choice columns, and 623 items.

SharePoint list Service Requests with Title, Status and Priority columns

Two details matter here. Status has three choices, and 623 rows is more than the 500-row default Power Apps reads, so it shows the row limit clearly.

Build the Demo App Step by Step

If you’ve never built a canvas app, start here. Go to make.powerapps.com, select Create in the left menu, then Create from blank.

Create an app page with the Create from blank canvas option highlighted

Studio opens, which is the app editor. On the command bar, select Add data, search for SharePoint, and pick the SharePoint connector. A data source is simply where the app reads its records.

Add data menu with SharePoint typed and the SharePoint connector highlighted

Paste your site URL when it asks, check the box next to your list, and select Connect.

Choose a list panel with Service Requests checked and the Connect button highlighted

Now select Insert and search for drop. You’ll see two controls: Dropdown under Input is the modern one, and Drop down under Classic is the older one. I use the modern control below and only bring in classic where it behaves differently.

Insert pane search for drop showing the modern Dropdown and the classic Drop down controls

For more on the newer control’s styling and theme settings, see my modern dropdown control guide.

Three moves you’ll repeat. Select a control, pick a property in the dropdown left of the fx formula bar, and type the formula. Select Play at the top right to run the app, and press Ctrl+S to save.

How Items, ItemDisplayText and Value Work

Items is the list of options. Everything else in this post depends on what shape that list is, so here’s the short version from my tests:

JobModern DropdownClassic Drop down
Set the optionsItemsItems
Pick the column to showItemDisplayText (a formula, such as ThisItem.Title)Value (a picker in the Properties pane)
Starting valueDefault, as a recordDefault, as plain text
Read the choiceSelectedSelected
Nothing chosen at startEmpty boxFirst item
Most items shownFollows the data row limit500, even at a higher limit

Note: classic’s Value isn’t a formula property. When I pasted it in control YAML, Studio refused it with “Unknown property ‘Value'”. On the classic control you set it from the Properties pane. There’s also no Fields setting on either dropdown, so column choice happens only through these two.

Method 1: Add Dropdown Values Manually

Use this when the options are short and never change, such as request categories. Select the dropdown, pick Items in the property list, and type your values as a table inside square brackets:

["Hardware", "Software", "Network", "Access"]
Items property of the modern dropdown set to a typed table of four values

In Preview, the list opens with exactly those four values.

Preview of the modern dropdown open and listing Hardware, Software, Network and Access

How does this work?

The square brackets make a one-column table, and Power Apps names that column Value. That’s why the display formula is ThisItem.Value, which the modern control needs here.

ThisItem.Value

Text needs double quotes. Without them, Power Apps reads the word as a name it can’t find.

Method 2: Dropdown Items From a SharePoint List Text Column

Use this when each option is a row in the list. Same Service Requests list, now showing its Title column. Set Items to the list name:

'Service Requests'
Items property of the modern dropdown set to the Service Requests list

Then pick ItemDisplayText in the property list and name the column:

ThisItem.Title
ItemDisplayText property of the modern dropdown set to ThisItem.Title

That lists every title, starting at Laptop replacement #1000.

How does this work?

Items now holds whole records, one per list row. ItemDisplayText runs once for each record, and ThisItem means the row being drawn, so the control shows that row’s Title.

The classic control does this differently. With the same Items, its Value picker chose Compliance Asset Id for me, an empty system column, so the box looked blank. Open the Value picker in the Properties pane and choose Title:

Classic dropdown Value picker open with Compliance Asset Id set and the Title column highlighted

Now the classic control shows Laptop replacement #1000.

Classic dropdown properties with Value set to Title and the title showing on the canvas

Need two columns in one line? I’ve covered showing multiple columns in a dropdown separately. Lookup columns take a slightly different route, explained in binding a SharePoint lookup column.

Method 3: Dropdown Items From a SharePoint Choice Column

Use this when the column is a Choice type, because you get the column’s defined options instead of rows. Same list, now the Status column:

Choices([@'Service Requests'].Status)
Items property of the modern dropdown set to the Choices function on the Status column

The list shows New, In Progress and Closed, once each, in the order they’re defined in SharePoint.

Preview of the Choices dropdown open and listing New, In Progress and Closed

How does this work?

Choices returns the column’s options as a table with a Value column. So the modern control’s ThisItem.Value works again, with no list rows involved.

The @ tells Power Apps you mean the data source, not a control with the same name. Choices also rejects a plain text column, so it won’t work on Title.

Method 4: Show Only Unique Values With Distinct

Use this when you want each value once from column data, which a plain list binding won’t give you. Same Status column, this time from the list rows:

Distinct('Service Requests', Status.Value)
Items property of the modern dropdown set to Distinct on Status.Value

You get three options again, but the order is New, Closed, In Progress, because Distinct uses the order each value first appears.

Preview of the Distinct dropdown open and listing New, Closed and In Progress

How does this work?

Distinct reads the rows and returns a one-column table named Value. It only reads up to the data row limit, so a value that first appears past that point goes missing with no warning. There’s a fuller walk-through of showing only unique values if you need it.

How to Get the Power Apps Dropdown Selected Value

Insert a Text control, select it, and set its Text property. Which formula you use depends on what’s in Items. When Items is a typed table, a Choices table or a Distinct table, use Value:

"Selected: " & ddManual.Selected.Value
Text property of a label reading ddManual.Selected.Value with the result Selected Access

I picked Access and the label read “Selected: Access”.

When Items is the list itself, Selected is the whole row, so use the column name. I picked the last row and got its title and ID:

"Selected: " & ddTitle.Selected.Title & " | ID " & ddTitle.Selected.ID
Preview showing selected values with an empty text Default next to a working record Default

If you use the wrong one, Studio tells you straight away:

ddTitle.Selected.Value
Error tooltip Name isn't valid, Value isn't recognized on a dropdown bound to the list

The message is “Name isn’t valid. ‘Value’ isn’t recognized.” The list has no column called Value, so name the real one.

To use the value in another control, reference it in a formula. In this gallery, Items filters the same list by the chosen status, so Closed shows only Closed requests. You’ll find more patterns in filtering a gallery with a dropdown.

Filter('Service Requests', Status.Value = ddStatus.Selected.Value)
Gallery filtered by the Status dropdown with a Rows for Closed count of 206 and a delegation warning

CountRows of that same Filter returned 206 for Closed, with a yellow triangle. That’s a Power Apps delegation warning, meaning SharePoint can’t do the counting for the app. The filter itself ran on the server, and the number was right.

Set the Power Apps Dropdown Default Value

This is where modern and classic differ most. On the modern control, a plain text Default fails:

"Closed"
Red error on a modern dropdown Default of text Closed: Expected a value compatible with Items

Studio says “Invalid formula. Expected a value compatible with ‘Items’.” and the box stays empty, even though Microsoft Learn shows a plain text Default for this control. The same text works on classic. Give the modern control a record:

{Value: "Closed"}
Default property of the modern dropdown set to the record Value Closed with Closed showing

That opens on Closed when Items is a typed table. On a Choices table the same record gave no error but stayed empty, so look the value up from the table instead:

LookUp(Choices([@'Service Requests'].Status), Value = "Closed")
Default property set to a LookUp on Choices with Closed selected in the dropdown

The classic control is simpler, and plain text works:

"Closed"
Classic dropdown Default property set to the text Closed with Closed showing

Values that aren’t in the list behave differently too. With a Default of Open, which isn’t a status, the classic control quietly showed the first item, New. The modern control with {Value: "Open"} stayed empty.

A default can also come from a variable, which has its own traps, so I’ve written about setting a dropdown default to a variable. For form-style defaults, see setting the default from a SharePoint list.

Pro Tip: A modern dropdown with no Default starts empty, so a filter on it returns no rows until someone chooses. The check for that is in testing whether a dropdown is empty.

What Happens Past 500 Rows: Modern vs Classic

Same Service Requests list, 623 items, both controls with Items set to the whole list. At the default data row limit of 500, both stopped at row 500, New hire setup #1494, with no delegation warning on either:

Modern dropdown list scrolled to the end at row limit 500, last item New hire setup #1494

Then I raised the data row limit to 2,000 under Settings > General and refreshed the data source in the Data pane.

Settings General page with the Data row limit box set to 2000

The modern dropdown then reached the very last row, item 623:

Modern dropdown at row limit 2000 reaching the last list item, LastSubmit demo VPN reset

The classic control did not. It still ended at row 500 and added a last line, “Maximum number of items reached”:

Classic dropdown at row limit 2000 ending at New hire setup #1494 with Maximum number of items reached

That matches Microsoft Learn’s 500-item maximum for classic. Learn lists the data row limit as up to 10,000, but Studio rejected anything above 2,000 when we tested in October 2026. I set mine back to 500.

Important: don’t solve this by raising the limit on a big list. A scrolling list of thousands is hard to use anyway. Narrow the Items formula with a Filter that SharePoint can run, like the Status filter above.

Which Method Should You Use?

Your optionsUseWhy
A short fixed listTyped tableNothing to connect
A SharePoint Choice columnChoicesAlways matches the column’s options
Rows in a listThe list with ItemDisplayTextYou can read any column from Selected
Repeated values in a columnDistinctOne entry per value, but capped by the row limit
Dependent dropdownsFilter in ItemsEach list narrows the next

For that last case, follow my guide to cascading dropdowns in Power Apps. I’d use the modern control on new screens, and keep classic for screens that already depend on it.

Things to Keep in Mind

  • A blank list usually means no column was named. Set ItemDisplayText, or the Value picker on classic.
  • On the modern control, use a record for Default. Plain text gives an error.
  • Use Selected.Value for typed, Choices and Distinct tables, and Selected.ColumnName for list rows.
  • Modern starts empty and classic starts on its first item, so check for blank before you filter.
  • A row past the data row limit is simply missing, and the list gave me no warning about it.

A few more dropdown tasks you may run into next:

Frequently Asked Questions

How do I add dropdown values manually in Power Apps?

Set the Items property to a table in square brackets, such as [“Hardware”, “Software”, “Network”, “Access”]. On the modern control, keep ItemDisplayText as ThisItem.Value.

How do I show SharePoint list items in a Power Apps dropdown?

Set Items to the list name, then set ItemDisplayText to the column, such as ThisItem.Title. On the classic control, choose the column in the Value picker. For a Choice column, use Choices([@’Service Requests’].Status).

How do I get the selected value of a dropdown in Power Apps?

Use DropdownName.Selected.Value for typed, Choices or Distinct tables. When Items is a list, use the column name instead, such as DropdownName.Selected.Title.

Why is my Power Apps dropdown blank?

Usually no display column is set. In our test, the classic control auto-picked an empty system column and showed nothing until we chose Title. A modern dropdown with no Default also starts empty.

Is there a limit on Power Apps dropdown items?

In our test on 623 rows, both controls stopped at 500 by default. At a limit of 2,000 the modern dropdown reached all 623, while classic stopped at 500. Microsoft documents the control properties in its Dropdown modern control reference.

Leave a Comment