Retain Field Ordering when Layer is Removed from a Map.

[Debert]

When pulling a Hosted Feature Layer through the AGOL Portal, the field order is not retained. This makes quality control and updating attributes more difficult, as users become accustomed to the familiar order of fields in the attribute table (e.g., beginning, middle, end). When the field order is lost, it significantly slows down the workflow and increases the potential for errors if extra attention is not paid.

I’ve tried multiple workflows to preserve the field order schema, but none have been successful.

An enhancement that retains field order when a layer is removed from a map would be extremely beneficial for our workflows.

A bug has been logged BUG-000172553.

I hope you'll consider this.

[CraigWilliams]

That issue ended up being converted to an enhancement ENH-000172553 which was then closed with the public explanation:

"This is the expected behavior. Fields cannot be permanently reordered at the database level.
https://support.esri.com/en-us/knowledge-base/how-to-permanently-reorder-fields-in-a-feature-class-u..."

Is something being lost in the communication here? If the desire is to save the field re-order, you can use a layer file for layer level re-ordering without altering schema.

[Debert]

Hi @CraigWilliams, thanks for attempting to clarify.

I'm still a bit confused as I previously attempted the workflow to permanently order fields using Export Features and they didn't stick. Again, the issue remains when pulling the Hosted Feature Layer through the AGOL Portal for edits- field ordering rearranges. Support also tested this and saw the same behavior.

As far as saving as an .lyrx, I've previously attempted that workflow as well. It's my understanding that the .lyrx is a symbology properties file and has nothing to do with the field ordering.

I'm really not sure what I'm missing here.