ArcGIS Pro coded value display sorted

418
6
05-27-2020 07:24 AM
Status: Implemented
Labels (1)
AJR
by
Occasional Contributor

When viewing a coded value domain that is based on an integer field in AGP, the values are sorted as if they are strings when displayed instead of by the actual integer (short or long) values that are the codes.  It would be much more useful to have them displayed in properly sorted numerical order.

Tags (2)
6 Comments
MarcelSt-Germain

Hum, for me text sort is fine so, make a choice.  Sort by values or by name.

KoryKramer
Status changed to: Needs Clarification

@AJR Sort was added in Pro 2.8.  See https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-attribute-do...

KoryKramer_0-1634907595625.png

 

Does that work for your use case?

AJR
by

omg, this is so much better!  Having the sorting is a nice addition, but the fact that in 2.8 the values are actually sorted by their numeric values rather than as strings is really the winning part of the update!

AJR_0-1634917353327.png

 

KoryKramer
Status changed to: Implemented

Great!  I'll mark this one implemented.  Thank you for the confirmation!

AJR
by

Unfortunately, it seems like the sorting uses string sorting rather than numeric sorting.  As soon as the codes are sorted they get all jumbled up again (string sort) and there doesn't seem to be any way to get back to the initial display of the properly numerically sorted values :(  For me, the update addresses the original issue of having the values numerically sorted rather than string sorted, but the implementation only seems to be about halfway there.  Anyone who wanted to see the list sorted in descending order (or sorted by description and then wanted to get back to the original ascending numeric sort) is out-of-luck.  The only way to get back to the properly ascending sorted numeric values seems to be to click on another domain and then click back to the domain of interest.

KoryKramer

Good catch @AJR I'm glad that the default sort for numeric codes addresses the original issue raised.  I've shared the point about the sort on integers behaving like a string sort with the dev team.

Thank you!