The default sorter for IP addresses in Alteryx is what you'd expect. It doesn't understand how octets work and sorts weirdly.
With this input list
| IP Addresses |
| 10.10.10.100 |
| 10.10.10.11 |
| 10.10.10.1 |
| 10.10.100.100 |
| 10.10.11.11 |
| 10.10.1.1 |
Alteryx will happily spit out this when you try to sort Ascending by IP Address.
| IP Address |
| 10.10.1.1 |
| 10.10.10.1 |
| 10.10.10.100 |
| 10.10.10.11 |
| 10.10.100.100 |
| 10.10.11.11 |
As you can see, it puts '100' before '11' in all cases because it is sorting each individual digit instead of each octet.
A super-simple way to fix this is to split the IP into individual octets and sort on those.
I broke it into octets using a regular expression.
(\d+)\.(\d+)\.(\d+)\.(\d+)
Using the Parse Output Method to create new columns from each octet.
Then you just sort ascending on 1st, 2nd, 3rd, then 4th and your list is sorted properly.
| IP Address |
| 10.10.1.1 |
| 10.10.10.1 |
| 10.10.10.11 |
| 10.10.10.100 |
| 10.10.11.11 |
| 10.10.100.100 |
Just leave the four extra columns off of your Select since they are extraneous.
I really wish Alteryx had an IP sort built-in, but it's easy enough to add this to any workflow working with IP addresses. If it were built-in, there could also be logic built in to identify valid and invalid IP addresses such that 265.354.25.1 would be rejected.
