Hi there -
We're slowly implementing feature services for editing use in ArcGIS Pro by GIS users in our organization. So far, we've come across 3 issues, any combination of which are a deal-breaker for most of our users migrating from ArcMap:
1. The inability to undo edits is super inconvenient, especially for beginner / intermediate users
2. Selecting a number of features at once (> 10) and doing a batch attribute update often results in waiting indefinitely for the edits to save..... resulting in lots of frustration.
3. The service is always editable... so for users who inadvertently do a copy and paste with a feature selected from that service, they've just duplicated data without ever having to click the "edit" tab.
We really don't want to use offline editing as a solution.
Does anyone have similar experiences with editing services? Any workarounds that we might try?
- Mike Knapp
Are these your observations as a power user setting these editable services up for the lower level users?
Or are these the results of the lower level users actually using these services and reporting back the problems they are facing?
Hi Michael... thanks for the reply.
These are the results of users actively using feature services in ArcGIS Pro and reporting these issues back to us as items they would like to see addressed.
"Selecting a number of features at once (> 10) and doing a batch attribute update often results in waiting indefinitely for the edits to save..... resulting in lots of frustration."
When you run Fiddler when making these batch edits, what are you seeing? I'm about to open up a case on this very issue....
Thanks Thomas.... we haven't run Fiddler on this at all. I've just been assuming that, since this happens during batch edit submittal via Pro or Web App that it has something to do with the submittal process. It's been pretty frustrating for our users, who often need to update 10-20 features at once. Although it doesn't seem to matter how many features are being updated at once.... it either takes a long time or doesn't work at all (spins endlessly). It might work once after the services are refreshed, but that's about it.