nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Update View" not displaying newly added fields in feature layer

IanGallo

After updating a freature layer via S123 connect, I cannot add the new fields to a view layer that I have been using with this project. The fields just don't show up in the "Update View" tool in AGOL. When I create a new View Layer from the Hosted Feature Layer, the new fields are available for use. Any way to fix the original view layer? It's a pain to recreate the view layer and remap all of the services that use it.

Not sure if relavent but one of the changes I made when adding new fields to the feature layer was enabling attachments on one of the related tables.

Will likely reach out to support on this and am still in the testing phase of this project but it would be great to know what to do if this ever comes up again in the future as this project will have a long lifespan. Any advice would be appreciated.

New View Layer.jpg

Original View Layer.jpg

protect-12-1

SpatialNinja_0-1720051939695.jpeg

Find more posts tagged with

Content Management

Sharing and collaboration

Data and services

Accepted answers

All comments

jcarlson

We see this a lot. Best practice is to add the new field from the layer's page in AGOL, which, somehow, makes the field available to your views.

When you add the field elsewhere, such as Pro or S123, and overwrite the layer, any dependent views will not see the new fields.

You can edit the layer JSON to include the new fields, using something like the AGO Assistant or the Python API.

IanGallo

@jcarlson Will take your advice in the future and see how that goes. Thanks!

I am a newer user and this is a bit of a frustrating theme with some attempts by Esri to makes things more user friendly in AGOL - the tools provided in AGOL don't work as intented or are unreliable which is not user fiendly at all! I would much rather be forced to learn how to do it the right way the first time instead of spending hours troubleshooting to learn that I just need to use a slightly more complex but way more reliable process in Pro instead of the AGOL based tool.

ZoevdbAT

Hi Josh,

I added new fields in AGOL and in my non editable view I was able to add the fields through update view. However in my editable views they failed to appear. I am looking for a solutions and came across your reply. Where in the AGOL assistent JSON file do I add the new field to the editable view? In the popupInfo?

I hope to hear from you!

- Zoë

IanGallo

Hi Zoë, Did you ever find out how to do this? I am running into the same issue.

jcarlson

Sorry for the delayed response, and thanks @IanGallo for getting this back on my radar.

It would appear that the AGO Assistant does not let you modify the view in this way, and I was confusing it with using the Python API. I use both frequently enough that I sometimes forget which functionality is in which place.

If you're comfortable using Python, check out the update_definition method of the FeatureLayerManager class.

source_fl = gis.content.get('itemid').layers[0] # or whatever layer index

source_field_props = source_fl.manager.properties['fields']

# You can modify the feature layer properties if you want

dest_fl = gis.content.get('itemid').layers[0] # or whatever layer index

dest_props = dest_fl.manager.properties
dest_props['fields'] = source_field_props

dest_fl.manager.update_definition(dest_props)

ZoevdbAT

Hi Josh,

Thank you for providing us the code to update the layers! However I agree with @IanGallo that this isn't very user friendly. You stated earlier that when adding the fields through AGOL you will be able to see them in the updated views, this isn't correct. I added new fields in the Layers page and they never appeared. Weirdly enough these fields are visible in the filter you can set in the update view window. So it does know the new field because u can use them for a filter (which you obviously can't use), but when in comes to adding new fields to the View it doesn't understand. Seems rather strange to me.

Maybe it's just a bug?

- Zoë

ZoevdbAT

I ended up creating a new view which had the new fields. But not even a week later I figured that I needed yet another field so I decided to just give up.

PanGIS

Hi @IanGallo have you solved?

I am replying in order to see if someone has something new to say.

It happens randomly and I can't figure out whether there is something wrong from my side.

I have a hosted feature layer with new fields and 1 view is used in a complex system of apps. I can't risk to lose everything by creating a new view.

All the other views can see the new fields (a couple of them where created at the same time with the one that doesn't work.)

I can't understand!

ZoevdbAT

The only update that I have is that there are more people who struggle with this Re: Hosted Feature Layer view can't be updated wit... - Esri Community

And that it probably is a bug.

We should file a report.

- Zoë

Esteban_Leguizamo

I'm not sure if you are still having this issue but I did come across it. While I was updating some workflows I needed a new field that had to be populated. I ran a SQL calculation and when I went to go update my filter criteria I noticed that the field count increased. I checked all my view layers and every single one can now populate.

Very odd but wanted to drop this off here in case anyone else has this issue. I am now setting a new field that can be used to just run a quick SQL calculation in my workflow if I need to add a new field. I replicated this with another feature layer and it worked. Hope this helps anyone else.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.