Unanswered

ComboBox limitations

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hello,

I am trying to build a combobox for a list of products. The list so far has over 5000 records. What are the combobox limitations for searching and displaying that amount a items? How can I make it work for us? The list might grow bigger once I add more companies to the list. Any help is appreciated

Categories:

Building Power Apps

I have the same question (0)

All responses (11)

Answers (0)

mdevaney 29,991 Moderator on at

Like (0)

Report
Copy link

Link copied!

@Anonymous
Your choice of datasource and the functions you decide to use in the Items property must be fully delegable. Other than that there would not be any issues caused by the datasource size.

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I am using a sharepoint list. I changed my limit to 2000 but If I search for a part I don't get a result because that part is not within the first 2000 but would the search find what contains that search record and return anything up to 2000 records? I guess I'm confused on how this really works.

Was this reply helpful? Yes No
mdevaney 29,991 Moderator on at

Like (0)

Report
Copy link

Link copied!
@Anonymous
Can you share your code from the following properties
DisplayFields
SearchFields
Items

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Items = Products.Name
DisplayFields = ["{Name}"]
SearchFields = ["{Name}"]

When I look at the sharepoint list, The product is actually "ProductID" but when I use it in PowerApps, I have to use "Name" to find the product. Could that be the problem?

Was this reply helpful? Yes No
mdevaney 29,991 Moderator on at

Like (0)

Report
Copy link

Link copied!
@Anonymous
I think its odd that you must write the Items with a dot in the middle to define a column name. Can you please try this instead and let me know the result? I would typically write it like this
Items: Products

Then I would reference the name in a label or other control like this.
ComboBox1.Selected.Name

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I made the changes you suggested and the search still can't find that product. I searched it in the sharepoint list and it's item 20,051

Was this reply helpful? Yes No
mdevaney 29,991 Moderator on at

Like (0)

Report
Copy link

Link copied!

@Anonymous
Sorry, I forgot something I should have already known on my initial response.. I forgot that SEARCH in a ComboBox + SharePoint List cannot be delegated meaning anything past 500 rows (or 2000 if you increase the settings) will not be considered in the search results. The only solution I know of is to change to another datasource where SEARCH can use delegation such as SQL or CDS but those do come with a cost $$$...

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I just read that too online. Or I could use StartsWith. We started this project with SQL but the cost of licenses made us move to Sharepoint but I think we might not be able to use sharepoint if we are trying to use lists that have more than 2,000 records and try to search for them. Does that sound correct?

Was this reply helpful? Yes No
mdevaney 29,991 Moderator on at

Like (1)

Report
Copy link

Link copied!
@Anonymous
StartsWith is definitely delegation friendly for SharePoint. Of course the limitation is the text string typed by the user cannot appear in the middle of the word. You could implement StartsWith in a ComboBox put putting this code in the Items property
Filter(your_datasource_name,StartsWith(your_column_name,ComboBox1.SearchText))

You are correct that SharePoint is not a great option if using SEARCH for more than 2,000+ records is a must. SQL or CDS would be the first choice but they carry additional expenses. My only other idea would be to somehow "pre-filter" the results so they are less than 2,000 when searched. For example: if we are searching for an employee located at an office we would filter on the office first to limit the number or employees being searched. Not ideal but it does OK in some scenarios.

Mr-Dang has a few posts about overcoming delegation by pulling records into a temporary collection. However in your case 20,000+ records might impact performance. (I've not done this yet so I cannot guide you through it. Just wanted to give you ideas.)
https://powerusers.microsoft.com/t5/Building-Power-Apps-Formerly/Overcoming-the-500-record-limit-locally/td-p/18379

If you'd like to see SEARCH be delegated in SharePoint suggest you go vote for an Idea like this one.
https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Search-function-delegation-for-Sharepoint/idi-p/107429

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

It's very frustrating that this is limited and SQL is premium. Looks like we might have to find another alternative. Thanks for your help and I just voted for this issue too!

Was this reply helpful? Yes No