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?