Currently the only option (that I'm aware of) to set feature service capabilities is at the service level. It would be very helpful to be able to control feature service capabilities at the layer level for referenced services published through ArcGIS Server.
The current hosted feature layer view capabilities have their use, but for enterprise/authoritative data used across multiple public and internal maps and applications, making a copy of the data to host in ArcGIS Online and then keeping it synced with an on-prem enterprise geodatabase feature class is not feasible.
I attached an overly simplistic image showing what ideally it would be helpful to do. In this use case, the same team is in charge of editing and updating the datasets. One requires the ability to move features, another should only permit attribute updates, and the third needs the ability to add new features. To make this work currently, you would need to publish three separate feature services, one for each combination of edit capabilities. Shared instances can help keep resource consumption down, but for organizing web GIS services being able to publish one feature service for one work area would be ideal.
In the past I've actually had to publish separate feature services to address this gap. That's no fun, it would be great to get a little more granular!
I completely agree, this functionality is desperately needed. Because of this limitation, we end up having much more overhead and more services to control specific permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.