So I had to update a dropdown list in a feature class. I updated the symbology in the hosted feature layer in AGOL and ensured it updated in the map. It looks fine in the legend too. And this is in both AGOL and Field Maps. However, when I go to add a new feature in the web map or Field Map, it only gives me the old list to select from. Where else do I need to make changes, or what else can I do?
My only other idea is perhaps I should just make the changes in ArcGIS Pro and use the Overwrite web layer option? Maybe that would make other changes within the hosted feature layer that would include updating the editing too?
Thank you.
Solved! Go to Solution.
Just confirming you updated the list on the field itself, and not just the symbology?
Otherwise it's likely that when adding a new feature, you are looking at the original feature templates on the layer. Templates are preconfigured features, most commonly made from the field driving symbology.
https://doc.arcgis.com/en/arcgis-online/manage-data/manage-feature-templates.htm
I believe you'll want to open the map in Field Maps web designer and update the templates there. It's a tab in the form.
I believe it's a migration issue between the map Viewer classic and new map viewer. They'll likely improve the experience and steps over time.
For now we configure the templates in Pro before publishing, and then at a map level in field maps web designer. I believe you can save back to the layer or use classic but agree with you, the paths are not always clear.
If this helped, please accept my answer as the solution so others can find the answer / see the post has been addressed.
Cheers, Chris
Just confirming you updated the list on the field itself, and not just the symbology?
Otherwise it's likely that when adding a new feature, you are looking at the original feature templates on the layer. Templates are preconfigured features, most commonly made from the field driving symbology.
https://doc.arcgis.com/en/arcgis-online/manage-data/manage-feature-templates.htm
I believe you'll want to open the map in Field Maps web designer and update the templates there. It's a tab in the form.
Correct, first I changed the list, then I changed the symbology.
You helped me find the solution, though somewhat indirectly, and still the behavior of this is strange to me...
So, according to the link you sent, managing feature templates for a layer is to be done either in ArcGIS Pro or AGOL's Map Viewer Classic. I wanted to see if this could all be done online, so I went to try that. However, several of my layers have settings so that Web Viewer Classic cannot handle them... so I could not manage the feature template. I click Edit and it still shows the old feature template.
The link says to go through the hosted feature layer, but the directions are not quite the same. There is an option to "Open in Web Viewer Classic with full editing control". I did this and this time when I clicked Edit, it showed the new feature template, and gave me the option to click Manage. So I clicked it, and then it gave me the option to Save, so I saved it. I didn't change anything there. But then when I went back to Map Viewer, the new feature template was there. Also, I refreshed the web map that this layer is part of, and also went into Field Maps and everything works now.
So the instructions in the link you provided are not updated to what I actually had to do, and I didn't actually need to do anything (because I made the changes in the layer's data and visualization), but it seems I did need to go through the process I outlined above.
So it works!!! So thank you very much!
I believe it's a migration issue between the map Viewer classic and new map viewer. They'll likely improve the experience and steps over time.
For now we configure the templates in Pro before publishing, and then at a map level in field maps web designer. I believe you can save back to the layer or use classic but agree with you, the paths are not always clear.
If this helped, please accept my answer as the solution so others can find the answer / see the post has been addressed.
Cheers, Chris