Spreadtables: Service Request and Tasks Not Sorted Properly by Number (i.e. Find Service Request, Tasks tab)
(Doc ID 2175680.1)
Last updated on FEBRUARY 06, 2022
Applies to:
Oracle Teleservice - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
Service Request (SR) or Tasks are not sorted in ascending/descending order properly based on SR or Task numbers.
For example:
In the "Find Service request" form, when searching for a SR by giving some parameters, the results are not sorted correctly when trying to arrange the results in ascending or descending order of the Service Request number.
Expected Behavior:
When you sort a set of SRs or Tasks (say 108743, 89786, 90312, 100337, 19824), the expected output would be:
19824
89786
90312
100337
108743
However, it considers all the elements starting with '1' as the lowest value, producing the following output:
100337
108743
19824
89786
90312
A similar behavior can be observed when using SQL*Plus, against the base views (JTF_TASKS_V or CS_INCIDENTS_ALL_B) and using ORDER BY TASK_NUMBER (or REQUEST_NUMBER).
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |