Are there any limits to the number of columns and rows in a WebListbox ? The LR does not say.
Not sure if there is an actual max, but in terms of making it useable, you should keep it under 50-100 rows at a time max and use pagination if at all possible.
You are quite right, Tom. As I am considering creating an improved WebListBox with the same features as the Desktop one, I am trying to make sure I am not missing anything.
Thank you.
I know where I remembered seeing a limit. Reading about Desktop listbox, it is mentioned that the maximum number of visible columns is 64…
if you transfer in chunks to browser, I think you can have thousands of rows.
But on the end the browser may get slow…
[quote=194014:@Christian Schmitz]if you transfer in chunks to browser, I think you can have thousands of rows.
But on the end the browser may get slow…[/quote]
I am just studying the project. I will probably paginate the visible rows.
On a desktop browser I limit the max number of rows to 3000, but it’ll go much higher. The main issue is the delay in how long it takes to add into your WebListBox from your database, then send the results down to your browser. I have sent down over 5000 rows, but there is a reasonable delay (~ 5-10 seconds).
I put a container of search fields next to the listbox. If there is text in it, then the XXX records returned must match those values.
I’m not sure if there will be problems on portable devices (RAM and network). I haven’t hit any, but in normal cases use less rather than more.
There is no limit, but as others have stated the control can get very sluggish with lots of data.