Select to view content in your preferred language

feature field order in mxd  not inherited in feature service after publishing

738
2
08-23-2012 02:18 AM
StefanThorn
New Contributor
In a mxd-project, I have several features classes available and put effort in the symbology, view range, which fields visible and field alias and the ordering of the fields in each feature class.

When publishing the project to an AGOL Description and create a map for this feature service everything looks ok. When, I look at the popups the field order is not inherited as set in the mxd for each feature layer in the feature service. This means, I have to overlook all layers in the feature service and again have to reorder the fields instead of only configure the pop ups a bit more fancy.

Who has this same experience and has a solution for this unwanted behavior?
Tags (2)
0 Kudos
2 Replies
BeckyHjelm
Deactivated User
Yes I am having the same problem. And reordering them thru the small dialog box in AGOl is very time consuming. The solution is ordering the fields the way you want them in the feature class or table.
0 Kudos
AndreRumpold
Deactivated User
... and all alias that i defined in mxd got lost.
0 Kudos