I'm having an issue where fields are editable in Pro and Online, but not Field Maps. There are no contingent values applied to fields for this feature or other effected features. See pictures and captions below.
Summited to pro as this is where I started this feature's life and therefore is the first place I could make a mistake upstream.
Accepted Solutions
My apologies, I wrote that original reply in a hurry, so I wasn't as thorough as I could have been.
Regarding the first question, I think it's possible that you didn't save the WebMap when you made the form, so it wasn't there when you revisited it. Otherwise, yeah, there's not a default form.
Regarding the second question: Pop-ups and forms are edited in two different places.
I'm going to answer the AGOL side first, then the Pro approach. (Things might change if you're publishing a service from an enterprise GDB, this covers hosted features on AGOL.)
AGOL:
So, the bad news is that you do need to configure the forms per map, per feature class, as best I can tell. Unfortunately, you can't configure the form as a default through the Visualization tab on the Item detail page.
However, you can convert the popup (Gonna cover editing the pop-up, too), and the pop-up can be set as a default. The work flow for configuring the popup for each individual map is the same, but you do in the webmap, not on the Item Details page.
- Go to the item's detail page, then click on the Visualization tab
- Select the layer you want, then click the "Pop-ups" button.
- My current pop-up looks like this:
- Go to Fields List
- I don't want to see the State (Field2) in my popup, so I'm going to remove it from the list
- After making your changes, save in the upper left
This has set the default pop-up for the layer. It can be customized in webmaps as desired.
Pro:
- Right click your layer and press " Configure Pop-ups"
- Turn off/on the fields you want
- Export to AGOL
Next steps:
Once you have your layer, put it in your webmap, create a form from the pop-up, and don't forget to save.
- Saving through the Webmap: Click okay, then save the map
- Saving through the FieldMaps website:
In this case, I want users to edit the State, but I don't want to see it after the fact. So I'm going to drag the field into the form, so it'll show up during collection, but not in the pop-up after collection. (You can of course make it so you can see things in the pop-u that aren't available during collection).
Final result:
Hope this helps!
That's a FieldMaps issue, but it should be pretty easily solved.
Either in the FieldMaps Site or from New Map Viewer , go to the form for the feature class.
FieldMaps web app
MapViewer
From there, you can add the fields to the form that you want
The second part, where the fields aren't visible after editing, is determined by your popup.
Apologies for the late response.
This is a good band aid, and may point to the deeper issue.
My main issue with this solution is that I would have to create a form for each of the ~20 features that I have, every time I upload a new project. That seems error prone and inefficient.
I don't know if it's correct that when I first entered the field map I was shown the message below. This tells me that despite seeing a form before setting this up, I have no forms. Is this normal or does it suggest I made an error in Pro?
You said that fields wouldn't be visible after editing and that this is a popup issue. I'm having a hard time finding the option to make it always visible.
Also, I asked the question in this community due to the suspicion that mistakes in Pro caused FieldMaps to not operate correctly.
My apologies, I wrote that original reply in a hurry, so I wasn't as thorough as I could have been.
Regarding the first question, I think it's possible that you didn't save the WebMap when you made the form, so it wasn't there when you revisited it. Otherwise, yeah, there's not a default form.
Regarding the second question: Pop-ups and forms are edited in two different places.
I'm going to answer the AGOL side first, then the Pro approach. (Things might change if you're publishing a service from an enterprise GDB, this covers hosted features on AGOL.)
AGOL:
So, the bad news is that you do need to configure the forms per map, per feature class, as best I can tell. Unfortunately, you can't configure the form as a default through the Visualization tab on the Item detail page.
However, you can convert the popup (Gonna cover editing the pop-up, too), and the pop-up can be set as a default. The work flow for configuring the popup for each individual map is the same, but you do in the webmap, not on the Item Details page.
- Go to the item's detail page, then click on the Visualization tab
- Select the layer you want, then click the "Pop-ups" button.
- My current pop-up looks like this:
- Go to Fields List
- I don't want to see the State (Field2) in my popup, so I'm going to remove it from the list
- After making your changes, save in the upper left
This has set the default pop-up for the layer. It can be customized in webmaps as desired.
Pro:
- Right click your layer and press " Configure Pop-ups"
- Turn off/on the fields you want
- Export to AGOL
Next steps:
Once you have your layer, put it in your webmap, create a form from the pop-up, and don't forget to save.
- Saving through the Webmap: Click okay, then save the map
- Saving through the FieldMaps website:
In this case, I want users to edit the State, but I don't want to see it after the fact. So I'm going to drag the field into the form, so it'll show up during collection, but not in the pop-up after collection. (You can of course make it so you can see things in the pop-u that aren't available during collection).
Final result:
Hope this helps!
