Question

"random" Sort order on Customer Support and Service Order list

  • 20 December 2022
  • 3 replies
  • 103 views
L
Rank
Userlevel 3
Badge +9

Hi,

 

Recently (we’ve updated customer to HF12 Nov 30th), we ‘ve noticed that the sort order in not fully exact, and changes when you move back to the previous result page and go to the next one again. Please see some examples :  

Records ordered by open date desc, from 41to 50 - 1rst time  : 

 Moving back to records 31-40

then moving forward again to 41-50

Again order is not good based on the time, BUT not the same as previously as it should. 

 

Customer uses a lot this feature. How can we fix quickly this issue ?

BR

Laurence

 

ALLIANCE V15.1.0.12

3 replies

L
Rank
Userlevel 3
Badge +9

well, there are other transactions on which the sort order is not good : have a look on this screenshot : 

 

A
Rank
Userlevel 7
Badge +10

well, there are other transactions on which the sort order is not good : have a look on this screenshot : 

 

Hi Laurence,

In this screen shot, it looks like you are sorting by two columns (Version and Date/Time). Can you remove the sort on the Version column (you can do this by clicking a few times on the column header until the arrow to the right of the column disappears). Then check if the Date/Time sorting is accurate once it’s the only column being sorted.

If the sorting is still inaccurate after all other column sort filters have been removed, please log a support ticket to investigate this fruther.

Thank you,
Andrew

Phil Seifert
Rank
Userlevel 7
Badge +21

Hi Laurence,

There is a ticket logged where it was found the sort order was not correct, especially when moving from one page to another, in the order locator for open datetime.  I suspect this is also coming into play with your situation.

Order Locator we see Open Date/Time which is fine, but sorting on this column goes wrong

This was confirmed on QAC and it is an issue that may impact other fields/modules besides the order locator Open Datetime.  R&D has assigned this to be fixed with SU5.

Reply


Terms & ConditionsCookie settings