That makes sense with the updates.
So where does the shape data come from in the excel file? Is it just lat/lon columns, or a location string?
Also, I don't use that same process w/ tabular data like Excel much, so I am wondering: does it prompt you to define the location fields each time?
I should say, "makes sense" doesn't necessarily mean that it's the intended outcome. I've run into lots of issues with the content on an Excel file being incorrectly inferred (string as integer, and vice versa) upon being published, where it changes a field type upon overwrite.
I could see a situation in which the contents of the spatial column in the uploaded file have changed, AGOL doesn't properly infer its spatial type, defaults it to some other column. Then, lacking a spatial component, keeps the resulting service as a table. Like I said, "makes sense" ≠ "the right result". Maybe "understandable" is a better word.
Since you're overwriting the service entirely, it's possible for basically everything about the layer to change. I've done overwrites going from points to polygons and back again, massively changing the schema each time.
- Josh Carlson
Kendall County GIS