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; } } }

Feature attribute update in 4.17

MKY

I'm using feature form to update attributes and it works fine in 4.16. I started getting an error after moving to 4.17. I can not make sense of the error.

Uncaught (in promise) -- cannot read property 'length' of undefined.

Also, After some time the view becomes unclickable.

Please see the attached image for details

I have a sample in codepen https://codepen.io/markoskifle/pen/PoNzmpm?editors=1000

2020-10-15_11-40-07.png

Find more posts tagged with

Accepted answers

HeatherGonzago

Just an FYI that this bug was patched and should no longer be happening when accessing 4.17.

All comments

MKY

Thank you.

HeatherGonzago

Just an FYI that this bug was patched and should no longer be happening when accessing 4.17.

HeatherGonzago

Ok, thanks Todd. Yes, this issue has been addressed. We plan on releasing a patch this week. I'm not sure of the exact date yet. Once it is finished, we'll make sure to note this thread as well.

ToddAtkins

Yes, we are observing this behavior on a service hosted on a 10.5.1 server that doesn't support pbf format.

HeatherGonzago

We intend to patch this. The problem is not with the FeatureForm, but rather the data that it is using.

The issue is that the featureLayer.applyEdits throws an error when service does not support f=pbf. Could you confirm if this is the case with the data you are using Todd?

ToddAtkins

Exact same here. We also saw that eventually the browser (Chrome) would crash with an "Oh snap" error on the page.

HeatherGonzago

Hi, I'm currently taking a look at this now and will let you know what we find ASAP.

Ok, so after some digging, this is definitely a regression (bug) that was introduced at 4.17. We are currently looking into the most feasible way to handle this problem. For now, my best suggestion is to stay at 4.16 for the time-being. We apologize for this and hope to get this addressed very soon.

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.