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 Layer View Field Length

IsaiahAguilera

We have a Feature Service in ArcGIS Online that has a field called "Description". This field had the default 255 string length. We also have a few different layer views referencing this item with different options and filtering turned on. We recently had to increase this field length to 2000. What we did was create a temp field and then calc the values of "Description" into this temp field. We then deleted and re-created the "Description" field and calc the values back into it. The problem is all the layer views referencing this feature service still have the length set at 255. Even though the original service now shows 2000 for the field length. Is there any way to force the update of the layer views service definitions to reflect the length update?

Thanks,

Isaiah

Find more posts tagged with

Accepted answers

Anonymous User

I reproduced this and logged an issue with our development team. It only happens if the field name is exactly the same.

All comments

Anonymous User

Did you go into the visualization tab for the views and select define fields? Fields added to the source layer are pushed to the views but they are not displayed by default.

Hosted feature view does not inherit new field added to hosted feature service

IsaiahAguilera

Well the problem for me in this instance is the field in question already existed. The field was deleted and then re-added with a different field string length but had an identical name to the previously deleted field. So the field shows in the view but it shows with the old length at 255 rather then the new length at 2000.

Anonymous User

I reproduced this and logged an issue with our development team. It only happens if the field name is exactly the same.

Anonymous User

Forgot to mention, in the meantime as a workaround you could create field with slightly different name or 1 added and keep the display name (alias) as description

IsaiahAguilera

Thanks for the advice. For our particular workflow we were wanting to avoid re-configuring all of the apps, web map, popups, etc to use the new field. That is why we named it exactly the same. We ended up recreating the view in question as this was easier then making a field with a different name. Thanks!

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.