This page describes search results in an MDriven application, not search for documentation pages in the wiki.
Application seeker search
Use OCLps to search for a subset of records in the database rather than loading a large set of rows into memory. Search and filtering are distinct from ordering: search uses a user-entered search word, while filtering uses a selected parameter or contextual reduction. Tables, search and ordering
Limit and page results
Use the MaxFetch tagged value to control the maximum number of records returned. If MaxFetch is not used, the documented default is 20 records. Search result pages
When paging is enabled, the seeker first obtains the total hit count. Paging uses variables for the result count, page length, page count, and requested page. Set the requested page before executing the search. To identify the grid that presents seeker results, add IsSeekerResultGrid=true to the grid nesting. The documentation states that this paging UI is available in the WPF client and Angular-Turnkey client. Search result pages
Order partial result sets on the server
If search, filtering, or pagination returns only part of the full result set, changing the sort order requires rerunning the search in the database. Sorting only the rows already loaded by the client does not sort the complete matching set. Tables, search and ordering
For example, the documentation describes a search with more than 1,000 matching people where only 100 rows are loaded. Sorting those loaded rows by last name does not produce the first 100 matching people by last name across the entire result set. Tables, search and ordering