Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts!
Lately I stated, that text-fileds are somehow sorted strange, if they start with numbers.
They are sorted like 1- 11- 12-...-2- 20- 21- 22- 23-...-3-...
Perhaps the number part of such text fields should be treated as a whole number not character wise.
this is supported in input lists. when you associate a list to a field, you can select the sort type. either "alphabetical order" or "entry order". alphabetical order will sort in the fashion you describe becasue this is the way that Windows works. Windows by default sorts exactly the way you describe.
however we solved this problem by providing the ability for a user to designate a specific order within the list and then selecting "Entry Order".
let's say that you create a list for Severity, which ranks from 1 to 10. enter the list items in the order you want: 1, 2,...10. when you associate this list to the Severity field, you'd get the list in order of 1,2,3,...10 if you select Entry Order. If you selected "Alphabetical Order" then you'd get 1,10,2,3,... per Windows.
if you are just sorting random data within WQS that is not tied to a list, such as part numbers, then you'll still get the standard Windows behavior.
Yes, I wanted to sort part numbers, as they are identifier fields, they behave like text fields and therefore are sorted the standard way.
But I got a workaround working, I created an automatic calculation, which translates the text/identifier field into a value field.
And this value field is the one I sort by and therefore I get a consecutive number sorting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.