We are at the point of our Utility Network migration for our utilities that we have published a utility network service that we can now use to create editing web maps for our field crews to use in Field Maps. Most of our web maps we only need to make attribute edits (no geometry edits), but we do have a few maps that will require both attribute and geometry edits.
Is it correct that the only way to control whether geometry edits can be made is on the settings of the published utility network service? And would we have to publish two utility network services, one with geometry edits enabled and another with them disabled, and pull in the appropriate service to the web map depending on what kind of edits we want allowed?
Solved! Go to Solution.
You can control the editing capabilities of each service by adjusting the feature service settings in Portal.
If you need to have separate behaviors for different web maps, then you will need to have different services. Which shouldn't be too big of a deal if you've been applying all your symbology and configuration using web maps and not at the service level (which is a best practice).
This approach makes sense because if we didn't make you publish separate services and instead tried to control it through the web map, a malicious user could directly access the service in the web map and make whatever edits they wanted.
You can control the editing capabilities of each service by adjusting the feature service settings in Portal.
If you need to have separate behaviors for different web maps, then you will need to have different services. Which shouldn't be too big of a deal if you've been applying all your symbology and configuration using web maps and not at the service level (which is a best practice).
This approach makes sense because if we didn't make you publish separate services and instead tried to control it through the web map, a malicious user could directly access the service in the web map and make whatever edits they wanted.
Thanks @RobertKrisher I thought that was the case but just wanted to make sure I wasn't missing something!