Accepted Solutions
Hi all,
This issue is planned to be addressed to some extent in the upcoming release (currently planned for tonight 12/8). With this fix, Map Viewer will honor the attribute fields configuration and won't allow editing fields that are set to not-editable in the pop up configuration for the feature layer.
In order to hide some attribute fields, you can use view layers and set attribute definitions. By doing so, the fields that are not included in the view layer won't be visible and hence not editable in the Map Viewer.
(*In the new release creating a view layer interface has been updated to provide a better user experience)
And... here is the more exciting part and a sneak peak to a new functionality in this ArcGIS Online release which provides a better experience for controlling fields visibility and editability.
Now you can use Forms (similar to what you might be already familiar with in Field Maps) in Map Viewer to control which field should be visible/editable on your map when adding/editing features.
I hope this answers your some of your questions and provides a viable solution. Please feel free to post any additional questions here or by reaching out to Technical Support.
All the best,
MJ
I can confirm similar behavior in my maps. If the layer is editable, all visible fields are editable.
The workaround here (warning: it's tedious) is that recently AGOL added the ability to toggle editing per field. So I guess it's more accurate to say, if the layer is editable, all visible fields are editable if their settings allow it.
Item → Data → Fields → Field → Editable
It's a really fantastic addition, and you'd only have to change it once per layer / view, but there's not really another way around it at this point.
To make it less tedious, you could do this via the Python API. If you look at FeatureLayer.manager.properties, you can find the fields section, which looks like this (emphasis added):
"fields": [
{
"name": "OBJECTID",
"type": "esriFieldTypeOID",
"actualType": "int",
"alias": "OBJECTID",
"sqlType": "sqlTypeInteger",
"nullable": false,
"editable": false,
"visible": true,
"domain": null,
"defaultValue": null
},Using update_definition, you can adjust the editable property that way as well. Depending on how many layers you're trying to update, it might be quicker to do up a python loop.
Same issue here. Setting the Editable setting on the layer itself is not an option as some fields need to be editable at other stages of our workflow.
Here is my configured pop-up:
When someone goes to edit this same point every single field in the feature layer is available for editing. I didn't include all fields but this demonstrates the issue.
This is not a good thing. I'd like to see my pop-up as configured above but only the fields that can be editable will be editable.
