I have the following problem: I need to display almost 5000 items in a ComboBox control (and allow users to use search on that ComboBox).
At first i noticed only 100 items where shown, but after i use SetSizeLimit(5000) that limit disappear. The problem is that when i load the model and try to open the ComboBox it freezes for a long time and behaves weirdly after: if it opens (only sometimes) i am not able to scroll, it closes itself, etc.
What I don't understand is that if this control is not designed to show many items, then which control is, or what does SAP recomends in this matter. It's easy to say, "filter your data before binding such a large model" but doesn't really apply to my app.
I encountered a similar situation. my work around was as follows:
1) I got a json string with all the records that needed to go into the combo box... i used a JSON model instead of the OData Model so that my search would be local to an array in the model, unlike the OData model which is a server side model.
2) on another scenario i had, i allow the users to start typing on the combo box control but i only filter records after they have typed more than 2 or 3 chars in the search box, that way i can minimize the filtered results and hopefully that is under > 1000 for a faster search.
in my case i had a combo box that had approx 28k records these were my approaches. i hope this helps you in some form .