danwallie

FeatureServer REST metadata scrambles type order

Discussion created by danwallie on Oct 20, 2011
Latest reply on Feb 27, 2012 by danwallie
I have published a FeatureService with a point class that has an unique value renderer with 26 unique values, one for each letter of the alphabet. The REST and HTML metadata both correctly order the Drawing Info:Renderer:Unique Value Infos, but strangely the Types are ordered

A-I,T-Z,J-S

which corresponds to ID's

1-9,20-26,10-19.

I have checked Domain values, MXD ordering, and everything I can to make sure that the incorrect order is nowhere else. Any idea why this would happen? PJson output is attached.

Attachments

Outcomes