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

Unable to save form changes

tendtreesTC

I have been working on a fieldmap app for a few weeks until suddenly a few days ago when I went to make a change to the and save the below error appeared stating that it was unable to say my form changes.

It is telling me to check the layer settings and confirm that I have the privileges required to make changes. The layer has been set to allow editing and I am an administrator.

Is there something I am missing here?

Find more posts tagged with

Accepted answers

All comments

AaronWorthley1

In case it helps anyone:

I just encountered this error with a hosted feature layer that is part of a field group with contingent values originally set up in Pro. After much experimenting I finally found the issue was a duplicate domain description- the codes were unique, but two codes had the same description text. This somehow caused the error in Field Maps Designer. I could add the form element for the field, and save the form, but if I tried to edit the element properties at all, it would throw the error and the form would not save. After making the domain descriptions unique, the error was gone.

SharonUngerer_DNREC

I also got this error while working in the Field Maps Designer. Opened up the web map and edited the Smart Form their and was able to save successfully. Console error I had below:

Kevin_MacLeod

Another helpful note - today I was getting this error. Turned out there was a Domain with two identical Descriptions. Apparently that causes this error. There was 14: Grease Trap and 15: Grease Trap for a sewer structure point layer with a domain categorizing the type of structure.

Field Maps Designer and Smart Forms are fantastic. Field Maps is coming along. (addition of more tools and perhaps customization of the interface a la WebApp Builder would be sweet but for now it gets the job done)

treistadbakk

Same problem. I just removed the attribute "Shape_Length/Area" as they are write protected. Works fine now!

JosephET

I just set up a Fieldmaps map with three editable layers in it - point/line/polygon.
The point and polygon layers set up forms without issue, but the line layer wouldn't save from the get go.

For me it turns out the issue was the Shape_Length field being included in the list of fields - once I removed that, I could save the form.

I don't quite understand why it had added itself, as the polygon layer didn't add either of Shape_Length or Shape_Area when generating the form - perhaps a little big Esri side..?

So long story short - perhaps try running through the fields one by one and see if any have the red asterisks in the Properties/Formatting pane on the right and remedying those, or removing the problem fields completely.

LanceKirby2

Same here.

JonathanMcD

Going to stick my hand up on this issue too, really frustrating.

AnaDeniston

Try to copy the JSON in the AGOL Assistant. By doing that you don't need to create the whole form again.

Regarding the 'save' issue, I am having the same problem.

SamiHammer

I'm having the same problem when I just need to delete a field from a form. Argh! Now instead of a 15 min project to edit the form a bit, I'm going to have to create a view layer, add it to the map, and redo the form.

ColinLawrence

Hi @Z-man , is this outside of the context of a reserved keyword? Do you have a reserved keyword on the switch type field? It would throw the same error regardless of field type.

However, I believe you have a different scenario here. Where is your data coming from? Were the coded value domains ever changed, like in Pro for example? Was the default value set in Pro or Designer? Any additional info would help us track this one down. Thanks!

Z-man

Are Switch input types also affected? Nothing has changed in the attached example and a default is set in the templates tab. 😑

switch.PNG

tendtreesTC

Yes that is my problem too. thank you for letting me know what the issue is and I look forward to the fix.

ColinLawrence

Great! Yep, that was not an intentional change. A fix should be deployed in the coming days which will continue to allow this configuration as before.

Z-man

ColinLawrence, you nailed it!

We had a field named "Year", a reserved SQL keyword. Removed and changed slightly. Although it's peculiar because that field has been in place for a long time and never caused the save issue or errored before. Oh well.

ColinLawrence

Do you see any other errors in your form in the Properties tab, for specific fields? There is a known issue where we are getting hung up on reserved keywords that we are working on fixing. If the fields are existing in the Feature service (ie published from Pro or another source) we should be ignoring this restriction when the form is saved. Example below:

ClayDonaldsonSWCA

I was able to resolve by removing the form elements and re-add them. Here is the error in the developer console. Really frustrating error. Hope ESRI pushes out a hotfix soon

t.4786-bc424acd4a43796192faeba6a2550bb5.js:1147 You are trying to log a non-primitive value, json:{"includesFieldGroupField":false}. This will get logged as [object Object]
(anonymous) @ ember-auto-import

Z-man

Exact same issue occurred to me this week.

Been using the same form for years and now 2/3 layers within a single shared feature service give me the error you mentioned (but 1/3 of the layers in that same FS save without the error).

Same editing and permission situation.

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.