You can temporarily override the Grid Layout customization sort by applying the sort criteria to the entire search result.
The following sort options are available for each column on the grid:
Sort Page Ascending: Arranges the current page of data in ascending order based on displayed values.
Sort Page Descending: Arranges the current page of data in descending order based on displayed values.
Sort All Ascending: Arranges the entire search result set in ascending order based on stored data values.
Sort All Descending: Arranges the entire search result set in descending order based on stored data values.
Notes:
The two Sort Page options apply the sort on just the current page’s set of data rows. This feature is expected to be used in cases where a user wants to temporarily view data within the current page using an alternate display sequence, but doesn’t want that criteria applied to the entire search result. Performing this sort should be rather quick. This option does not affect the order of rows in any other page.
The two Sort All options perform the column sort on the entire search result by re-executing the grid’s associated search with a temporary override to the ‘order by’ clause. If the user navigates to another page in the search result set, the column sort criteria is preserved. Performing this sort may take some time to execute when the number of search results is high. This option may cause objects that previously appeared on page 1 to appear on a different page.
The Sort All behavior is the equivalent to changing the list sort criteria, except that the adjustment is not permanent (that is, does not affect other instances of the entity grid). Columns where the field is a True/False flag or a defined by a Transportation Manager Domain Table are ‘grouped’ as opposed to sorted and may display in a non-alphabetical order.
The Sort Page behavior is slightly different. These options perform an alphabetical sort on one page of data using the actual displayed value, not the stored value. So enumerated and Boolean fields may appear in an order on the page that does not match what you might see if the same data was returned on a single page using Sort All.