ArcGIS Pro could maintain layer field order and alias when sharing web layer with time zone specified
Like Respect MXD field's order in MapService and FeatureService REST description which appears to have been implemented in ArcGIS 10.8. I checked with ArcMap 10.8 (to an ArcGIS Online hosted feature service).
The data source field order was changed in the layer so that Date_Field3 is before Field2 which is before Field1.
This is what I see in ArcGIS Online:
The shape_area, shape_length and objectID fields are still ordered last:
In ArcGIS Pro 2.5, I see the layer order respected in the hosted feature service:
I checked with aliases too and those come through as expected:
Hi Tim,
In my comment above I noted that the fix is in ArcGIS 10.8.
Your steps indicate you are publishing to ArcGIS Enterprise 10.7.1.
Below I published from ArcGIS Pro 2.5 to ArcGIS Enterprise 10.8.
Is that what you expect to see?
Hi Kory,
Well, bummer. Nope, my idea remains quite valid in my opinion. I found an ArcGIS Enterprise 8 environment that I could test with. Getting into a little computer science here...
- hypothesis: Kory is right and Tim is wrong
- test: using WA-DNR's county boundaries (WA County Boundaries ) as the source feature class, import it to an ArcGIS Pro 2.5 file geodatabase, then share as web layer to an ArcGIS Enterprise 8 deployment. Check the position and name of the date column before and after. If the position and name of the date column has changed, then the hypothesis is disproven.
- results: hypothesis is disproven
Interesting!
So I DO see what you see when I follow the steps that you provided.
Here is the difference in the testing that we were doing independently: since the idea was about changing field order, I had been changing the field order of the layer in Pro before sharing. And even when the Time Zone was set in my tests, I never saw it result in sending the date field to the end of the table.
Since I was finally able to reproduce what you see, given that I knew what I had tested previously, I decided to change the field order of the layer in Pro before sharing. When I do that, even with the Time Zone set (in this specific instance, I didn't check the Daylight savings box), the field order of the layer and the alias are maintained.
Then, even if I just use the Reset Field Order command to revert the layer's field order back to the database order:
publishing the layer still maintains the expected field order and does not alter the alias.
To demonstrate the repro steps you've outlined, if I remove the layer, and add the feature class back to the map and do nothing to the layer order, publishing results in the date field being moved to the end of the table with a different alias.
Given that, if you want to keep this as an idea open to voting by the community, a more descriptive title might be, "Maintain layer field order when sharing web layer with time zone specified" Seems like a very niche case for an idea, though.
If you agree, I could update the title and change the status back to (thoroughly) Reviewed. Or if you'd prefer to update the title, you can do that and then ping me to reset the status.
Thank you!
