Select to view content in your preferred language

Polygon layer in a feature service suddenly became uneditabe

657
5
Jump to solution
03-11-2026 08:37 AM
HanliePetoors
Frequent Contributor

Hi,

I'm working with a hosted feature service in AGOL. It has three layers, one each for points, lines and polygons.

On Tuesday the polygon layer suddenly become uneditable, both attributes and geometry. The other two layers are still editable.

When I try to edit it in ArcGIS Pro, I get the message in the attached image. This is a red herring because no relationship classes are present in the data, and, on Monday it was working fine.

I downloaded the data and ran check geometry on all three feature classes. The polygon layer did have some errors, mostly self-intersections.

At the REST endpoint the updateFeatures and addFeatures operations for the polygon layer give the message 'This operation is not supported.'

What can I do to fix this so that the polygon layer becomes editable again?

I don't want to create a new service with a new item id - this service is used in many maps, apps and web tools.

Thanks

Hanlie 

 

 
 
 

 

 

 

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
EmilyGeo
Esri Regular Contributor

No problem. It would be helpful to see the layer in order to figure out what's going on. Please reach out to tech support for help troubleshooting.  

View solution in original post

0 Kudos
5 Replies
EmilyGeo
Esri Regular Contributor

Hi @HanliePetoors

It sounds like its not working as it should. Can you share a link to the layer or a map?

0 Kudos
HanliePetoors
Frequent Contributor

@EmilyGeo thanks for the reply.

Unfortunately the data belongs to a client who is not willing to share it publicly.

The search continues...

0 Kudos
EmilyGeo
Esri Regular Contributor

No problem. It would be helpful to see the layer in order to figure out what's going on. Please reach out to tech support for help troubleshooting.  

0 Kudos
HanliePetoors
Frequent Contributor

In case this helps anyone, switching off all editing and switching it back on again on the settings page resolved this issue.

EmilyGeo
Esri Regular Contributor

Thanks for sharing @HanliePetoors I'm glad that you were able to get it working again 😊

0 Kudos