Would you be able to show a screenshot of the error? Since it is working with less rows, is server side pagination an option for you to work around this?
We do not necessarily have a specific number of rows that can be returned in a query, but our current table component is often not very performant with large datasets like this (in which case, I'd recommend pagination or filtering). We’re currently working on a new version of our Table component, which will be more performant. To share where we’re at in development, our new Table component supports scrolling up to 500K rows and includes 11 of our most popular cell types (Number, Text, DateTime, HTML, etc). It also supports basic column functionality (resizing, reordering, pinning, hiding, data alignment), single column sorting, select row and cell event handlers, theming, and keyboard navigation. We're looking forward to releasing this upgraded component once we've added more functionality & done more beta testing. Hope that context is helpful!
Hi @ritvik_singhvi Apologies about not posting back here for cloud! My notification on this thread didn't go through . The new table will be coming to on-prem in a few versions from now! (after v2.123)