SA-3769

Summary

The property pyResolvedTime is used in a listview for reporting. In the List view when pagination is enabled with SortMode as Allpages. Sorting on the property .pyResolvedTime property gives inconsistent result.

Error Messages

NA

Steps to Reproduce

1. Create a ListView using the property pyResolvedTime
2. enabled pagination with Sort Mode as AllPages
3. Run the report and click on Sorting options

Root Cause

When pagination is enabled and the SORT MODE is "All Pages", sorting is done in database operations, in which the sort order is case sensitive across all pages of retrieved data. The reason behind inconsistent data on sort is that the property pyResolvedTime has a controls ElapsedSeconds that formats the output into number of days.

If the format ElapsedSeconds is removed from pyResolvedTime and sort, sorting works fine, again since this is database sorting with order by, it is case sensitive.

If the SORT MODE is "Viewed Page", there is a server code to sort the data on each individual page, which can be set to be case insensitive. This works fine along with using the ElapsedSeconds format as well.

Further help note for sort options on listview.

* All Pages to cause clicking a column header at runtime to sort the entire result set of rows, rather than the current page. Sorting is performed by database software, and requires all data to be retrieved. Select this mode only when all properties in the report display correspond to exposed columns and use ordinary sorting rather than a custom sort routine (such as used — for example — by theWork-.pyID property for work object ID).

Resolution

If the SORT MODE is "Viewed Page", there is a server code to sort the data on each individual page, which can be set to be case insensitive. This works fine along with using the ElapsedSeconds format as well.