Field Maps Designer won't save form changes

[DanGruber]

Using AGOL I created a map with one editable layer and then opened the map in Field Maps Designer. I created a very extensive form with many fields, groups, conditional visibility, etc. Early on I was able to save the form periodically to the map and the layer, but as I progressed both options were grayed out. I need to save the entire final form to the map and the layer to be able to use it in the field.

What am I doing wrong or overlooking? Is there some limit to the number of times a form can be saved or how large a form can be saved.

Thanks for any help you can give me.

Dan

[JayHodny]

I had this issue occur in Field Maps on ArcGIS Enterprise 10.9.1 yesterday, and again today.  I was saving after every edit I made, then I noticed at some point the save button was greyed out.  I think this occurred after I added a new group.  Noting a comment in an earlier post, I deleted the group, and the save button was restored.  I did not save, but clicked the undo button, and restored my work in progress.  I then saved my work.  I did not lose my group or the edits I had made within the group.

[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.

[sam-gartrell]

I've been up against an issue like this several times in the past week and finally found a solution. I know it's consistently the same beacuse every time I encounter it, I open dev tools and see the following in the console: "relative url not supporterd in web map." Expanding the details of the error shows a relative URL that apparently isn't working: "./4be84b828d7a439dabb7bf1f45d8e2a1."The error is always repeated once for every layer in the map that my FM app is pointed at, with a unique failing URL for each layer. 

The solution that always works for me is to rename my web map, and then "Save As" the original name. Then point field maps at the new version of the map and off you go.

I hope they fix this soon--I'm wondering if the relative URL bug has to do with moving your web map to a new folder, where the relative URLs are severed from whatever root value is stored in the web map for their source.