I have a table that will be holding up to 35k entries. I want the user to filter it until he gets close or exactly where he wants, then run a query using that table’s filtered data.
When I enable filter data it is too large at first and I get gateway connection errors. Makes sense, so I want to disable filter results until I get a reasonably sized filter list.
However, I don’t see a means of seeing how many rows fit the filter criteria unless I enable filter data. I can’t just go by length of tiler, because some entries still have a large number of filters until you get to the last couple of characters, and that could be a large or small number of characters in that filter entry
Hopefully I have explained this well enough, if you need a sample let me know.
Thanks
The table filtering happens in the client and with any large(ish) data set, the result will break the websocket. It sends the result set back through the websocket uncompressed and doesn’t chunk the data to the configured websocket message size. You can increase the size of the websocket messages in the gateway config, but it will eventually break the session on you. It’s safest to not use the filtered data property of the table at all.
I’ve found the best thing to do is add a text input field and filter the data going into the table yourself on the gateway. You will have more control that way. It’s not ideal, but it is a safer way. If the websocket breaks, it will fully nerf the session.
Yes, that nerfing of the session is what I have experienced. I’ve modified it so that they use the text filter to narrow it down, and then action is taken when they click on an entry. I will keep your manual method in mind for next time.