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

What causes a Form and the '+" button to disappear?

MikeSlattery

I am not sure exactly why, but the Form I built is gone in the Field Maps configure pane for the layer, and so is the "plus" button in the Field Maps app. This has happened before, but I am at a loss to pinpoint the before/after scenario.

I did update the popup in the beta map viewer, and I did add a field to the layer - but there is no indication of why the whole Form is gone as if I hadn't built one.

Once I added the new field to the feature item definitions for the layer, I could add/edit features in the web beta, but there is stlll no Plus button on the app.

To my knowledge no one used the layer in the non-beta map viewer.

Najděte více příspěvků označených jako

Accepted answers

MikeSlattery

Hi @KevinBurke and fellow mappers: close or reload the tab on a new beta web map after naming and saving!

Here is something reproducible for me in FF and Chrome. Start a new beta web map, name and save it. As long as you keep that same tab open without reloading, you will clobber the form in a new Field Maps instance for that map with every change to the beta map in that tab!

Make a manual form, or convert, save and it will behave in iOS. But make any change to that beta map in that open tab, including renderers, etc. and the FM form will get clobbered. Close that tab and re-open the beta map in a new tab, or even reload that tab, and you can make changes to your FM form, and your beta web popup and the FM form will not get clobbered.

This works even if you create and keep open the beta web map in Firefox, and edit and save the new Field Maps instance in Chrome!

That first open tab, as long as it is open and not reloaded, has different side effects for a map save than a new tab or the same tab if reloaded.

fklotz

Further research has shown that our issue seems to be related to the following: Our maps were to be used in ArcGIS Field Maps only, we did not want the users to open them in Collector. So we unchecked the 'Use in Collector' at the bottom of the settings section of the map details page. When we do that, the "+" button disappears in ArcGIS Field Maps. Re-checking the 'Use in Collector' causes the "+" button to reappear.

I have a bug report in to ESRI with respect to this.

Current solution to get the "+" button to show: Enable "Use in Collector" for your map.

All comments

KevinBurke

@MikeSlattery

Thank you for sharing that information with us.

I am not sure at this point if these two issues are related or not. In the absence of the smart form, you should still see the normal editable popup. The fact that you cannot edit, seems unrelated to the missing form, at least at this point.

Can you confirm that the layer loads successfully without errors in the Field Maps mobile app?

If possible, would you be able to share the web map/feature services with me to take a look on my end?

If so, please invite the user ArcGISFieldMaps into a group.

Thank you

-Kevin

MikeSlattery

Thank you Kevin,

I have added that user to the group.

I have since rebuilt a smaller form. (There were 89 fields before - the collapsing fieldgroups are very helpful to the user.) I can add and edit points in the map viewer beta using that form. The 'assets_and_tasks_beta' map loads in the mobile app and the points update when data changes. But the layer is ReadOnly. The definition and checkboxes say otherwise, but there is that layerOverride array which includes 'capabilities' which I am giving the side-eye to right now. I hope this is not RTM territory and I thank you for looking!

Group: '5539155f79d540988348b2064bdf6c0b'

Map: '82d3dcac9abd451fbb32dbeb20e9dc09'

Layer: 'edda2ce07ee346ee9a8c69927e16f4bd'

MikeSlattery

Looks like you are right - the forms and the ReadOnly issue are separate. This entry just follows up on the forms/fieldmaps info removals. A fresh layer remained editable throughout.

Looks like any save on the Map in Beta Viewer removes the form from the Field Maps configuration for that map. The Summary addition I made also disappeared which seems consistent.

I started fresh with a new layer and map. I configured a popup in the Beta Map Viewer, saved and looked on the Field Maps App. I could Add points there. I then engaged Field Maps to create a form from that popup. Then saved it. I found that I forgot one field, so I added it to the form in Field Maps and saved it. Then I went back to the Beta Map Viewer and added that field to the popup and saved. I went back to the Field Maps front page and selected the new map. The form was gone.

I could still add/edit in the Field Maps App. I went back and re-created the form via popup in Field Maps, and that form was visible in the Field Maps App.

I added more layers and changed basemap in the Beta Map Viewer and saved. Going back in Field Maps from the map list to the map to the config, the form is gone again.

I still see the Add button in the Field Maps App, but the form is gone there too after restarting the app.

I updated the Summary for the map in Field Apps, but that went away as well.

Thanks again @KevinBurke and team for your attention.

MikeSlattery

@KevinBurke - I am able to edit both sides of the Beta Map/Field Map pair in Firefox with a copy of the new map without the resetting issue, and everything behaves in the App so far. This might point to a browser/caching issue in Chrome?

Version 88.0.4324.96 (Official Build) (x86_64) on OSX 10.15.7 Catalina

(Using Chrome for the FieldMaps and Beta Map pages, launching devtools to show network activity with cache disabled for each page used, seems to behave as well.)

KevinBurke

Hi @MikeSlattery

Thank you for that detailed information.

On the topic of the layer being editable vs read-only for the assets-and-tasks-beta map, I can reproduce the issue using that map in Field Maps for both iOS and Android. However when I saved a new copy of map using the Map Viewer Beta, I could no longer reproduce the issue, as you've stated as well.

When comparing the JSON of the Web Maps, in your copy I noticed it shows:

authoringApp: "ArcGIS API for JavaScript"

authoringAppVersion: "4.18"

In the new copy of the map I saved, it shows:

authoringApp: "ArcGISMapViewerBeta"

authoringAppVersion: "8.3"

I am not sure this is the cause of the issue or not, but I am curious how your original map was created? Which application generated that original Web Map?

For the second issue with the clearing of the formInfo in the Web Map JSON, I am trying to reproduce this behavior but haven't so far. I have a few more things to try, so I will keep you posted on this one. However in general the form information shouldn't be cleared when saving the map through the Map Viewer Beta. It will, however, if saved through the Classic Map Viewer.

Thank you

-Kevin

MikeSlattery

Hi @KevinBurke,

I did briefly use the map in a Web AppBuilder app to try the edit widget on it, before I started on the Beta Viewer/Field Maps process. Maybe the Javascript API value came from that exercise?

And I have had problems with Chrome cache on Macs before on various apps - not just arcgis - all over the place including local dev. I should I have isolated that sooner.

kmsmikrud

Hello,

I just wanted to add that I am also experiencing forms consistently disappearing after I have configured/saved within the Field Maps web app. I've looked at the map viewer beta and have made changes, but then when I go back to the forms they don't exist and back to square one. I have repeated this process already way too many times this morning. Why are the forms being dropped over and over? I know this isn't quite the same issue as the post, but it partially matches. Thanks

KevinBurke

Hi @kmsmikrud

Thank you for the additional information. I am investigating which workflows in the Map Viewer Beta (MVB for short) cause the form to get removed from the web map.

Can you please provide me with your repro case(s) for where you've experienced the form being removed?

Thank you

-Kevin

KevinBurke

@kmsmikrud are you working with related tables in the map?

kmsmikrud

Hi @KevinBurke ,

Thanks for the replies! I'm trying to reproduce the issue with the form being dropped, but of course its not happening at the moment. I do have 1 related table in the map. Thanks for your willingness to look into this. Are there any known workflows for Map Viewer Beta (MVB) removing the form? I'm setting up a number of maps for field work and forms dropping were/are troubling in trying to keep up with it all.

Thank-you,

Kathy

KevinBurke

That's what I am currently trying to figure out, is what workflows are clearing the form information when saving through the Map Viewer Beta.

Obviously if you save the map using the current Map Viewer it will clear the form information, but you should be notified when opening a map that has a form already configured in that case.

Internally we've had folks report an issue where the form is removed after having saved through the Map Viewer Beta after they opened a previously created map with a custom popup from the current map viewer and made changes to the popup configuration.

I did reproduce this once, but not repetitively, so I am still trying to narrow it down.

But perhaps this happens when making changes for existing maps using the Map Viewer Beta version.

Thanks for helping to try and narrow this down.

-Kevin

kmsmikrud

Hi @KevinBurke ,

In creating another web map today in Map Viewer Beta and then configuring the form in Field Maps all was well until I realized I needed to add filters to the layers in MVB. After I did this, the forms were gone in Field Maps. I also wanted to add a label for one of the layers, this also removed the forms in Field Maps. I will let you know what else I find.

Thanks,

Kathy

KevinBurke

Thank you @kmsmikrud!

I will check this out on my end as well.

kmsmikrud

Much appreciated! I also just renamed the pop-up title for a layer in MVB and this also removed the form on all layers. It doesn't seem like it takes much of a change in MVB at all for the form to disappear. Thanks for your help.

KevinBurke

Hi @kmsmikrud

Would it be possible for you to share a copy of a map, that has a form already created, that I can test with to try and reproduce this behavior? So far I've tried editing maps in the MVB that have smart forms built but I cannot seem to reproduce the clearing of the form as easily as you can. Therefore perhaps it has to do with the map itself as oppose to a general problem.

If so, please share with the ArcGISFieldMaps user in a group.

Also, if you can share a quick video of the editing done in the MVB and then how the form is removed through Field Maps (web application) that would be very helpful as well in trying to narrow this behavior down.

Thank you for your help on this.

-Kevin

Peters_Amy

Kevin, I have experienced the same behavior but in the regular AGOL web map, not even the Beta Viewer. Any change to anything in the web map with a resave will cause the Field Maps form to disappear. If you change a popup, layer name, filter, symbology, etc and resave, the Field Maps form will be gone and you have to start over. I could share my project with you but I can't afford to risk it getting deleted again. I don't understand how to make copies of the items for you. Would you like me to share the originals and you can make copies for your testing?

Amy Peters

KevinBurke

Hi @Peters_Amy

Thank you for the feedback. When it comes to working with smart forms and using the current Map Viewer, upon opening the map you should receive a notification indicating that the map contains certain functionality that's not supported by that version of the map viewer. In this case the smart form configuration is not supported by the current Map Viewer and, as a result, will be removed upon saving.

Therefore this is expected behavior for the current Map Viewer, and what I am trying to determine based off previous reports is why/how for certain situations the form is also getting removed after re-saving through the Map Viewer Beta (MVB). The form information should remain upon saving in the MVB, and indeed it does in general, however I am trying to understand the situations when it doesn't.

If you've seen this happen using the MVB, then I would like to understand the workflow you did there and try to replicate on my end.

On a side note, if you have already configured a smart form for a web map and would like to make a copy of that map, you should be able to perform a Save As using the MVB and not the current map viewer and the form should be retained.

Thank you

-Kevin

Peters_Amy

Kevin,

This is extremely helpful, thanks for taking the time to explain. I will try that Save As using the MVB.

kmsmikrud

Hi @KevinBurke ,

Apologies on the delay. I will follow up more on this next week as I need to create other projects with similar forms for different areas. I will take a video of editing and also share a map with the ArcGISFieldMaps user in the group. Thanks for the outreach!

Kathy

MikeSlattery

Hi @KevinBurke and fellow mappers: close or reload the tab on a new beta web map after naming and saving!

This works even if you create and keep open the beta web map in Firefox, and edit and save the new Field Maps instance in Chrome!

That first open tab, as long as it is open and not reloaded, has different side effects for a map save than a new tab or the same tab if reloaded.

fklotz

In case others encounter the missing "Add Features" or "+" button button after saving their ArcGIS Field Maps map, we've found that opening the map in Map Viewer BETA and saving as a new map has resolved this issue for us and the button shows in the new map.

It would be nice to figure this out without creating a new map with a new item ID and having to delete the old map and then rename the new map.

EmmaSchultz1

Hello @fklotz

Thank you for this suggestion. I am experiencing the same issue today. A little background on my web map/ field app map:

- Map was originally created in the Current Web Map. I configured the forms in Field Apps by converting my pop ups from this original map. I then wanted to try the Map Viewer Beta, which worked great but I noticed my "Search Features by Layer" options disappeared when I used the Map Viewer Beta. I reopened the map in the Current Map Viewer, saved it, and I was able to Search by Feature Layer again.

- Because of this, I was going to keep using the Current Map Viewer instead of Map Viewer Beta. However, I try to open the Field Maps app today, and the "+" "Collect" button has disappeared. I tried to open and save the map in Map Viewer Beta again, checked everything in the web Field Apps, opened the mobile App, and it is still not there.

Emma

fklotz

I have a bug report in to ESRI with respect to this.

Current solution to get the "+" button to show: Enable "Use in Collector" for your map.

EmmaSchultz1

Thank you for this solution. I definitely unchecked the collector option while configuring Field Maps. I will be sure to re-check this option.

fklotz

ESRI has now logged this as BUG-000137974

BUG-000137974: In the map's settings in ArcGIS Online, when the 'Us.. (esri.com)

BK710

Kevin,

My FieldMaps app is also missing the "+" sign for initiating collection of new points. The app is loading fine elsewise. I have both use for Collector and Field Maps checked in the settings, and editing was enabled when publishing. This is my first time experiencing the missing + sign

KevinBurke

Hi,

I also wanted to share that in the recent release of ArcGIS Online, if an existing map that includes a configured smart form is opened in the Classic Map Viewer, if that map were saved through that version of the map viewer, the form information should no longer be removed. Prior to this release, this was not the case and you would lose the form if the map were saved using the Classic MV.

Thanks

-Kevin

fklotz

@KevinBurke Would you be able to point to us to an online resource explaining this? Currently, there is still a warning when you open a Map Viewer map in Map Viewer Classic: "This web map includes configurations that are only supported in the new Map Viewer. To ensure the best experience, open the web map in the new Map Viewer." And on the compatibility matrix page it recommends you to "save as" if editing your map in a different map viewer. I'm concerned about losing map settings/functionality if I have to take my map back to Classic Map Viewer to edit something that is not available in Map Viewer.

martinserych

I have also problem with "+" for collecting data in my Field maps app. I do not understand how to fix it. Please help me.

link to the map: https://mendelu.maps.arcgis.com/apps/mapviewer/index.html?webmap=86c000b3b79d45dfbfa56bd0d6756092

fklotz

Hi, it looks like your layer might not be set as editable. It has to be editable for the + button to appear.

FionaRenton1

I have this same issue in ArcGIS Enterprise 10.9. It is a bit of a paradox

Katherine_Rudzki

Reporting in from 2024, this issue is still persisting. Has there been any progress in fixing this bug? It's incredibly annoying if you have a little change to make in a popup and your entire Field Maps Designer form is wiped.

NickMcNamara

June 2025, still a major issue. Any news, Esri? This is really really bad.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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