Enhancement: Allow fields selection & filters before opening data inspector

[StevenHit]

Hi, The object inspector suffers extreme slowness for bigger tables (many fields, many records), making it unusable for the consultant. It sometimes even gives memory errors. It would be nice if we can specify the fields and filters before opening the "data inspector" page. Doing so, we can limit the data shown, avoiding the latencies/errors. Thanks to consider this ;-)

[hougaard]

It's a good suggestion, I have been annoyed about this myself.

I have never seen memory errors, do you mind pasting them here?

Question, the data inspector is showing up to 50 columns right now, I could double the speed(and half the memory consumption) by reducing it to only 25 columns, would the speed increase warrant the lost of columns?

[StevenHit]

I have just tried it with a big table. You see chrome taking up to 6GB of memory until it shows this message:

Limiting the number of columns to 25 could help. But allowing the user to specify fields & filter before showing the data would even be better ;-).

[jn-khd]

Hi Erik, I would like to add my vote for this function. In some tables, some of our customers has over 100.000 records. It doesn't timeout, but takes a long time. Then afterwards filterering to the record i need, can be a hazzle. I'm on the On-premises version 1.0.0.232. So setting the filter before the Records load could be a fantastic feature.