ComboBox

[Anonymous]

Hi guys,

 Need some help please. I have an Excel workbook with around 7000 rows. When i create a combobox for one of the columns, the drop down menu shows me like a few hundered records i think. Is there a limitation here ? or is there any formula that i need to input to see all the values ? 

[Jeremy_Rodgers]

Hi Babalaul,

I have tried this today with a 10000 row Excel table and I was able to see all of the rows in the combobox drop-down.  There should not be a limitation to how many rows you can display, Items property should be set to the name of the Excel table.  It's possible there is something in the data that is causing an issue.  If you can share the Excel file with me I can have a look.

Thanks,

Jeremy

[Anonymous · Accepted solution]

You might have an issue with Delegation.

Links:

https://docs.microsoft.com/en-us/powerapps/delegation-overview

https://blog.coeo.com/davidmorrison/2017/06/21/powerapps-500-record-limit-delegation-and-how-to-work...

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Fix-500-Record-Limitation/idi-p/38490

tl;dr For some functions, only the first 500 rows are returned. That's a known issue and I don't think it has been solved before. In any case, if you want to use more than 500 records, you would have to limit yourself to using delegable functions.

Edit. Added another link.

[Anonymous]

Thank you

[Anonymous]

I will try to sort out data again and see if that will help. 

[Anonymous]

Again, I don't know about the specifics of your problem but if it's a problem with delegation, the issue would be with the formulas, not the actual data. Just so you know.

[JRaasumaa]

---

@Anonymous wrote:

You might have an issue with Delegation.

Links:

https://docs.microsoft.com/en-us/powerapps/delegation-overview

https://blog.coeo.com/davidmorrison/2017/06/21/powerapps-500-record-limit-delegation-and-how-to-work-around-it

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Fix-500-Record-Limitation/idi-p/38490

tl;dr For some functions, only the first 500 rows are returned. That's a known issue and I don't think it has been solved before. In any case, if you want to use more than 500 records, you would have to limit yourself to using delegable functions.

Edit. Added another link.

---

Based on the list of actual delegable sources it seems excel isn't in the list.

https://docs.microsoft.com/en-us/powerapps/delegation-list

I'd say that's definitely the issue here. Nice work!

[ttwydi]

Hi,

I have the same issue but using a Sharepoint List, for which I thought the combobox items were delegable. Instead I only get the first 500 hundred employees from my list in my combobox. I understand I could raise that to 2000, but I need to go above that.

I just put the formula Items = Employees, with Employees the name of my sharepoint list.

What am I missing?

Thanks,

Jerome

[vwyankee]

It's extremely frustrating to search threads to find where some state a combobox works fine for more than the app row limit (500 default) items to search/choose from and others report that it doesn't work. Like a couple have noted on here it doesn't work for me connected to a SharePoint list even with no operators in the formula - just datasource.column. I've see some say "just put it in a collection..." but that's limited as well (for me). I can use a search box but I'm trying to create a consistent interface for the user with various filters since another delegation issue is the search operator against a SharePoint list. 

These inconsistencies cause me to go DAYS with trying to come up with what should be a simple solution. If someone would be kind enough to point out how you can use a combobox for selecting more than the row limit with a SharePoint list as a datasource I'm sure many would really appreciate it. Alternatively, point us to documentation that shows it's not possible, please.

[Anonymous]

I fully agree with your frustration. There seems to be few inconsistencies in the behaviour of PowerApps. If you use the native environment for adding datasource to combobox (meaning that PowerApps do all the work) you may end up with the field Items referring only to the name of the list in Sharepoint (e.g. Contracts) and not with the explicit reference (e.g. [@Contracts].Title). I think (but this is assumption only) that if you are to use the native Title column in the dropbox (the column that is 'alway there'), PowerApps omit the second argument, which is fine (dropbox will still function as expected), yet the yellow traingle will appear. The triangle will disappear if you provide the explicit reference in the Item field (i.e. [@<NameOfTheList>].<NameOfTheColumn>