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

How to Build a Cascading Dropdown in Power Apps from a SharePoint List

Our help desk form had one drop-down with 14 request types, and people kept picking Printer for a VPN problem. The service desk lead asked for a category first, then only the subcategories that belong to it.

In this tutorial, we’ll build a cascading dropdown in Power Apps: two modern drop-downs fed by a SharePoint list, where the second one lists only the rows that match the first pick. Pick Software, and you see Microsoft Teams, Outlook, Excel and Power BI, nothing else.

You’ll create the list, add it to an app, wire both drop-downs, reset the child when the parent changes, and then try two variants: a cascade inside one list and a typed list with Switch.

Here’s what we’re building:

Finished cascading drop-downs in Preview showing You picked Software and Excel
  • Category (parent): Hardware, Software, Access or Network.
  • Subcategory (child): only the rows for that category.
  • A Text control that confirms the pair, here “You picked: Software > Excel”.

Before You Start: Create the Request Categories List

You need a Power Apps license that lets you build canvas apps and edit rights on a SharePoint site. We use our responsive app, SPGuides Responsive Demo, with modern controls turned on (the Power Apps modern dropdown control post covers that control on its own).

The data lives in one new SharePoint list on /sites/SPGuides called Request Categories. Each row is one subcategory, and a Choice column says which category it belongs to:

ColumnTypeNotes
TitleSingle line of text (built in)The subcategory, e.g. Laptop
CategoryChoiceHardware, Software, Access, Network

We added 14 rows. A Choice column is a column with a fixed list of options; Power Apps reads each value as a small record, which matters in Step 4.

CategorySubcategories (Title)
HardwareLaptop, Monitor, Docking station, Printer
SoftwareMicrosoft Teams, Outlook, Excel, Power BI
AccessSharePoint site, Shared mailbox, Security group
NetworkVPN, Wi-Fi, Remote desktop

To build it yourself:

  1. On your SharePoint site, select New > List, pick Blank list, name it Request Categories and select Create.
  2. Select Add column, pick Choice, then Next. Name it Category and type the four choices.
  3. Add the 14 rows from the table, typing the subcategory in Title.
Request Categories SharePoint list with Title subcategories and the Category choice column

New to building apps on a list? Our guide to create a canvas app from a SharePoint list walks through the app side from zero.

Step 1: Add the SharePoint List to Your App

A data source is the connection that lets your app read a list. Open the app in Power Apps Studio (the editor at make.powerapps.com) and select Data on the left rail.

  1. Select Add data, search for SharePoint and pick the SharePoint connector.
  2. Under Recent sites, pick your site (ours is SPGuides), or paste its URL and select Connect.
  3. In Choose a list, type Request in the search box and select the check box for Request Categories.
  4. Select Connect.
Choose a list panel with IT Help Requests and Request Categories checked and the Connect button

We checked IT Help Requests too because the same app uses it in our show and hide fields by dropdown demo; you only need Request Categories here.

Checkpoint: a banner says The data source “Request Categories” was added to your app, and the list shows under Data.

Step 2: Add a Header and Footer Screen

On the command bar, select New screen and pick Header and footer under Layouts.

New screen menu in Power Apps Studio with the Header and footer layout highlighted

The screen arrives with three stacked containers: header, main section and footer. A container groups controls and lines them up for you, so the screen reflows on a phone (more in our Power Apps container guide).

In the main section we added cards (auto-layout containers with a gap of 24 and padding of 24) for the parent and child. Each card holds a heading, a drop-down and a Text control. We named the screen scrCascading in the Tree view.

To add a drop-down, select a card, open Insert, search drop and pick Dropdown under Input (the modern one). Rename the two controls ddCaCat and ddCaSub in the Tree view so the formulas read clearly. Press Ctrl+S to save.

Step 3: Fill the Parent Drop-Down With the Categories

Select ddCaCat. The box to the left of fx on the formula bar is the property dropdown: pick Items there, then type:

Choices([@'Request Categories'].Category)
Items property of ddCaCat set to Choices of the Request Categories Category column

The Power Apps Choices function returns the options of a Choice column as a one-column table named Value. The @ and brackets just point at the list by name. You don’t need ItemDisplayText here, since it defaults to ThisItem.Value.

Checkpoint: in the editor, ddCaCat lists Hardware, Software, Access and Network. It starts blank because a modern drop-down has no default pick.

Step 4: Filter the Child Drop-Down by the Parent

Select ddCaSub, pick Items and type the filter. It keeps only the rows whose Category matches the parent’s pick:

Filter(
    'Request Categories',
    Category.Value = ddCaCat.Selected.Value
)

Then pick ItemDisplayText (the text shown for each row) and set it to the Title column, because each row is now a whole list item:

ThisItem.Title
Items of ddCaSub set to Filter on Request Categories with the pane showing Depends on ddCaCat

Category.Value is the text inside the Choice record, and ddCaCat.Selected.Value is the parent’s pick. Compare those two and the filter works; we got no delegation warning (the yellow triangle Power Apps shows when SharePoint can’t do the filtering, see Power Apps delegation).

The properties pane now shows Data source Request Categories and Depends on ddCaCat. The Text control under the child shows the pair:

"You picked: " & ddCaCat.Selected.Value & " > " & ddCaSub.Selected.Title

Checkpoint: with nothing picked in the parent, the child list is empty. That’s the filter matching no rows, not an error.

Step 5: Reset the Child When the Parent Changes

Select ddCaCat again, pick OnChange and type:

Reset(ddCaSub)
OnChange property of ddCaCat set to Reset of ddCaSub in the formula bar

OnChange runs every time the user picks a different value. Reset puts a control back to its Default, and our child has no Default, so it goes blank. Reset only works in behavior formulas like OnChange or OnSelect, never in Items (the same function clears a Power Apps combo box).

Checkpoint: no red underline on the formula. Press Ctrl+S.

Test the Cascading Dropdowns

Select Play at the top right (or hold Alt and click a control in the editor) to run the screen. Pick Hardware in the parent and open the child:

Preview with Hardware picked and the child list showing Laptop, Monitor, Docking station and Printer

It lists exactly Laptop, Monitor, Docking station and Printer. Picking Docking station changed the label to “You picked: Hardware > Docking station”.

Now switch the parent to Software. The child went blank right away, and the label read “You picked: Software >”. Opening the child showed Microsoft Teams, Outlook, Excel and Power BI:

Preview after switching to Software with the child blank and Microsoft Teams, Outlook, Excel and Power BI listed

Picking Excel gave “You picked: Software > Excel”, the result at the top of this post. To stop a save while the child is still blank, test IsBlank(ddCaSub.Selected); we cover that in check if a Power Apps dropdown is empty.

No Blank Option Needed: Modern Drop-Downs Start Empty

Older cascading posts (ours included) added a blank first row with Ungroup and Table so the drop-downs didn’t open on a value. Modern drop-downs don’t need that. With no Default they start empty, and after a pick an X button at the right of the box clears it.

Note: a classic Drop down shows its first item instead of blank, which is why we built this on modern controls. Our post on how to set a dropdown default value to blank has the classic workaround if you’re stuck on an older app.

Variation: Cascade Inside One List (Service Requests)

You don’t always need a second list. On card 3 we pointed a parent at the Status column of our Service Requests list, and the child at the same list’s rows:

Choices([@'Service Requests'].Status)
Filter(
    'Service Requests',
    Status.Value = ddCaStatus.Selected.Value
)

ItemDisplayText is ThisItem.Title again, and the label reads three columns from the picked record:

"ID " & ddCaReq.Selected.ID & " | " & ddCaReq.Selected.Status.Value & " | " & ddCaReq.Selected.Priority.Value

Closed listed Password reset #1005, New hire setup #1002, SharePoint site request #1008, Dock not charging #1011 and more. Picking Password reset #1005 showed “ID 2 | Closed | High”.

We left out the Reset on purpose here. When we changed the status to New, the modern child cleared itself anyway and the label dropped to “ID | |”:

Same-list cascade with Status New and the child drop-down cleared, label showing ID with empty values

So the modern drop-down drops a pick that isn’t in its new Items. I still keep Reset in the parent’s OnChange, because it states the intent and doesn’t depend on that behavior. The same Status filter drives a gallery in filter a gallery by dropdown.

Variation: Typed Lists With Switch (No Data Source)

For short, fixed lists you can skip SharePoint. On card 5, ddCaRegion has ["West", "Midwest", "South", "Northeast"] in Items and Reset(ddCaState) in OnChange. ddCaState picks its list with Switch:

Switch(
    ddCaRegion.Selected.Value,
    "West", ["California", "Oregon", "Washington"],
    "Midwest", ["Illinois", "Ohio", "Michigan"],
    "South", ["Texas", "Florida", "Georgia"],
    "Northeast", ["New York", "Massachusetts", "Pennsylvania"]
)
Switch formula on the Items property of ddCaState returning states for each region

Switch compares the region with each match in turn and returns the list next to the first one that fits. Picking South gave Texas, Florida and Georgia:

Preview with South picked and the state drop-down listing Texas, Florida and Georgia

This is handy for a demo, but every change means editing the app. If the pairs already sit in a Power Apps collection, use the same Filter pattern as Step 4 on the collection.

Using a Lookup Column Instead of a Choice Column

Some lists link the child to a separate parent list with a Lookup column (a column that points at another list’s rows). The shape stays the same: compare the lookup’s Value with the parent pick. For a Country list and a State list with a Country lookup, the child’s Items would be:

Filter(
    'Employee State',
    Country.Value = ddCountry.Selected.Title
)

We didn’t build this one in today’s demo, so check it in Preview on your own lists. For binding the lookup itself, see bind a SharePoint lookup column to a dropdown.

What About Cascading Dropdowns in a SharePoint List Form?

A lot of people search for SharePoint cascading lookups. The standard list form has no setting that filters one column’s choices by another. The route Microsoft documents is customizing the form with Power Apps from the list’s Integrate menu, and then the same Filter + Reset pattern applies.

Our walkthrough to customize SharePoint list forms with Power Apps shows that path. If you can’t use Power Apps, read SharePoint list cascading dropdown without Power Apps.

Building a SharePoint web part instead? That’s code, not formulas, and our SPFx cascading dropdown tutorial covers it.

Troubleshooting

  • Child list is empty. Nothing is picked in the parent yet, or you compared Category instead of Category.Value. A Choice column is a record; compare its Value.
  • “Name isn’t valid. ‘Value’ isn’t recognized.” You used ddCaSub.Selected.Value on a list-bound drop-down. Use a real column such as Selected.Title.
  • Child shows blank rows. ItemDisplayText is still the default. Set it to ThisItem.Title.
  • Old pick stays after the parent changes. Add Reset(ddCaSub) to the parent’s OnChange.
  • Reset gives an error. It sits in Items or Default. Move it to OnChange.

Important: Choices can’t be delegated, which is fine for four categories. For a parent list with thousands of rows, add that list as its own data source and filter it directly.

Where to Take It Next

Once the pair works, use the category to show only the fields that matter, then save both picks with a form or Patch when the user submits. If the form also needs several apps picked at once, see how to concatenate combo box values with a custom value.

You’ll find more drop-down and form builds in our Power Apps tutorials.

A few drop-down tricks that pair well with a cascade:

Frequently Asked Questions

How do I create a cascading dropdown in Power Apps?

Fill the parent’s Items with the categories, for example Choices([@’Request Categories’].Category). Set the child’s Items to Filter(‘Request Categories’, Category.Value = ddCaCat.Selected.Value) and its ItemDisplayText to ThisItem.Title, then add Reset(ddCaSub) to the parent’s OnChange.

How do I make a Power Apps cascading dropdown from a SharePoint list?

Add the list as a data source (Add data > SharePoint > Choose a list), then filter the child drop-down on the list’s Choice or Lookup column. Compare the column’s Value with the parent’s Selected.Value.

Do I need Reset on the child drop-down?

It’s the clean way. Reset puts the child back to its Default, which is blank on a modern drop-down, and it only runs in behavior formulas such as OnChange (Reset function). In our test the modern child also cleared itself without it.

Can a SharePoint list do cascading dropdowns without Power Apps?

Not with the standard list form settings. Customize the form with Power Apps from the Integrate menu, or use a script-based form if Power Apps isn’t an option.

Why doesn’t my filter on a SharePoint Choice column work?

A Choice value is a record, so compare Category.Value, not Category. Also set ItemDisplayText to the column you want to show; Microsoft lists it in the Dropdown modern control reference.

1 thought on “How to Build a Cascading Dropdown in Power Apps from a SharePoint List”

Leave a Comment