01-30-2013 01:31 PM
I believe this has been reported; not sure what the defect # is. The issue, if I recall correctly, is that the Sortable property is set to True in 8.0 for some grids; it should be set to False for performance reasons.
01-30-2013 01:45 PM
Thanks Mike.....and what happens for mulitple page selects if Sortable isn't set to true.....we were getting horribly inconsistent results for multipage selections within a grid in the 'old' days......
It is good to see that Columnar sorts are being done locally as a gridname. recordset.sort Field1......much faster than going back to the server for an ORDER BY sort AND having to go through the row by row SECCODEID and Field Level Security scrutiny (row level SQL Transactions + SLX OLE DB Provider interaction on rows and field values) that you just went through with the same recordset on the load of the grid.....
01-30-2013 02:59 PM
The following is the official answer: The Sortable property was set to True to address navigational and scrolling performance with a tradeoff of a degradation in loading performance; the default configuration should work best for most customers.
In other words, in comes down to fine-tuning/customization in the end, based on customer needs.
01-30-2013 04:52 PM
This all sounds fine and good... BUT it is not documented anywhere - ex: not documented in SLX 8.0 release/notes for upgrade nor in the training/re-cert for v8.0 on SageU.
I wonder how many other (un-documented) changes were made in 8.0 that we will all have to discover the hard way (wasting hours and $$$ in the process).
01-30-2013 05:00 PM
Ouch Mike! this was NOT documented in any 8.0 release notes......
And no mention that the Notes History Grid still has 2 Unnecessary round trip retrievals for every 1\single refresh of the grid....yes it's BADFAD, been around for years, and is a major factor in poor grid performance for larger retrieved recordsets....but if Sortable T F is a design decision, so should best practices for a grid be showcased in the base SLX product.