Sorting in list view may show duplicate records on multiple pages when using pagination

If sorting is done in list view, duplicate records are shown on multiple pages when using pagination and clicking 'Next'.

1. Go to incident_list.do.
2. Ensure that you have a number of records over 50.
3. Click the context menu (burger) icon next to the Incident form title and choose Show > 20 rows per page.
4. Click the Priority column header and choose Sort a-z (ascending).
5. In a new tab go to incident_list.do and open the same incident selected in step 3.
6. Click the right arrow to go to the next page.
7. Compare the records from the first page and the second page. Duplicate records appear in the first 20 records and the next 20 records.

This is due to a system design limitation, known since 2017, that affects the user experience when trying to see all matching query results.

Server-side pagination does not occur, when advancing a list result page, the server may re-send the same record again to the UI requesting a set of records.

When using the up and down (next and previous) arrows in the header of a record, the order in which the records are displayed may differ from the order in which they are returned. Users may see the same record twice in a row, or jump around in the result set, or even occasionally miss records when at the end of the list when multiple records have the same value for the datetime field. The 'next record' button on the top right corner returns a random order for those records having the same datetime value.

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

The workarounds is the following:

1. Set the system property glide.secondary.query.sysid to true
   
2. Set the below User Preferences to ensure there is always a default sorting based on the "name" field:
   • sysapproval_approver.db.order = name
   • sysapproval_approver.db.order.direction = DESC
3. Perform an instance cache flush