Form Builder is not showing all Fields

[ShoNuff]

I am trying to use the Form Builder in our Portal web maps to automatically calculate the Latitude and Longitude upon creation/edit of a point in a signs layer. The fields are not available in the Form Builder. I checked the source feature class in the database and both of the fields can be edited. (Please see the attached image.)

I can understand why the fields marked as Read Only are not showing up. Does anybody know why the Latitude and Longitude fields don't show up? I did not have a problem using the Smart Editor in Web App Builder (WAB), but since ESRI is retiring WAB I am migrating this to an Experience.

[Ed_ · Accepted solution]

just out of curiosity what if you create a duplicate of those two fields and see if the duplicates show? 

[ShoNuff]

That worked. I wonder if the original Lat/Long fields were created using a tool in ArcGIS Pro. Below, I included a link to the page that talks about esrignss fields.

FYI, I had to create a copy of the layer since I was not the owner. It behaved the same as the original layer.

It is a little puzzling because I was able to edit these fields in the Web App Builder version of the app.

Thanks for your reply!

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-gps-metadata-fields.htm

[Ed_]

No worries, I am glad it worked out 🙂. Please click on "Accept as Solution" the previous response as it worked for you. 

[ShoNuff]

I would still like to know why it's not working with the Form Builder. The fields seem identical.

Thanks again. This could be a good option for the users.

[kmsmikrud]

Hi @ShoNuff ,

I am having the same issue except its in the AGOL Field Maps designer for the gnss metadata fields like esrignss_latitude, esrignss_longiutde....etc. This is true in a number of layers that have the GNSS metadata added. I wanted to add arcade expressions if the values were null but looks like I can't even add them to the form. Interesting

Thanks,

Kathy

[ShoNuff]

Hi Kathy,

It looks like related behavior. I do wonder if ESRI chose to exclude those fields on purpose. I could understand this if they had them update automatically but this is not the case. I am wondering if this needs to be accomplished via attribute rules. I just did not want to have to do this.

Thanks for the feedback. If I find anything different I will provide an update.

-Manny