Showing results for 
Search instead for 
Did you mean: 
Post Prodigy
Post Prodigy

What is the best way to populate multiple custom dropdown menus in a form?

When I was working in PowerApps for Teams I had a form that had multiple custom datacards. Many of these datacards used comboboxes/dropdowns. At the time I was creating a unique table for each of these controls. I am now wondering if that makes the most sense. I could add a column for each set of values in a single table but I realize that the longest column of values is going to set the list length for each control leaving the smaller controls with a lot of blank items(without employing any kind of formula). I was thinking it might break with cascading controls but I guess that doesn't really matter.


What is the best way to populate these controls? A table for each control or a single table for all controls?

Super User
Super User



Look at it in the terms of amount of data instead of a set rule for this way or that.  If your total amount of items for all the dropdowns/combos is not going to incur any delegation issues, then a single table with all the values for the controls is fine.  If the lists can get long, then a separate list might be beneficial.


It's kind of like looking at the Distinct function.  It is not delegable.  So if your list is bigger than 2000 records, then Distinct will not be accurate.  So, you need to provide an alternate method.  This is usually done with a separate list that simply contains the distinct values that you want.  That list will be considerably smaller and more manageable - and delegable. 


I hope this is helpful for you.

(AND....yes, I'm back.  I will be starting to chew through my backlog of message, including yours, over the next several days and next week.  So, hang tight!)


Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
Post Prodigy
Post Prodigy

Sorry I never got back to this. I was giving more thought to this and I guess having dependent fields could be a problem with a single data source. I was also thinking from a reusability standpoint that it might also make sense to have separate tables. It also makes easier to find the data you might want to consume if it was in a table named specifically for the data it holds.

Helpful resources

UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Top Solution Authors
Top Kudoed Authors
Users online (2,376)