Issues with sorting on text fields that contain numbers

Bugs
1

Hi Team!

There is an issue when sorting text fields, whereby they aren’t sorted alphanumerically. You’ll see in the screenshot below that 11 is the second record when it should be the last.

image
image138×533 3.52 KB

2

Hey @EthosLuke - if you change your ‘Page Order’ field to a number field this won’t be a problem.

I see you’ve got 5b in that case you’ll need to pad your numbers to get the sorting you want in Noloco, such as 01, 02

3

Hey @darragh,

Is there any possibility of natural sort ordering for text fields being introduced? I don’t think padding the fields will be particularly easy to automate (using AT formulas), a generic padding to make all the values the same length doesn’t work as the values suffixed with letter(s) need to have more leading zero’s in order to be sorted correctly with basic alpha sorting.

image
image765×688 13.4 KB

4

Ok wasn’t as difficult as I thought, with the help of Regex! Below is the formula on my padded order field if anyone runs into the same issue:

IF(
  REGEX_MATCH({Page order},"\\d"),
  IF(
    REGEX_MATCH({Page order},"[^\\d*]"),
    RIGHT("0000"&REGEX_EXTRACT({Page order},"[\\d*]"),4)&REGEX_EXTRACT({Page order},"[^\\d*]"),
    RIGHT("0000"&{Page order},4)
  ),
  {Page order}
)
5

Actually I should have suggested just creating another column which strips the letters, so 3a becomes 3 that way you can sort on that number column and display your non-padded number

Assuming you don’t mind too much if 3a comes before or after 3 etc…

6

I’m jupping in with my question about sorting fields with special caracteres, like the print bellow:
image

The filter show Águas after Vitral

1 Like
7

I also have the same problem with Turkish characters: ÇŞİĞ, they all sorted after A-Z.