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

Error in Forms forcing me to have Object ID in the form as a required field

KaraUtter

Object ID used to not be a required field for a form to be valid. I have been trying to create a form for my field crew without forcing them to have to view the confusing objectID on their end, but for some reason forms will not allow me to delete ObjectID from the form. It sends the below error and then all my form configurations are gone and I have to start over. Why did this start happening and can we get rid of the requirement please?

Encuentra más publicaciones etiquetadas con

Accepted answers

KaraUtter

Apparently, the ObjectID field that came in as a Long field from the joined table, was also marked as not allowing NULL values due to it's original status as the unique identifier for the other table/feature that was joined. This being marked as not allowing NULL is what made it come through Field Maps forms as a required field. If it allowed Null values, it would not have been required.

KaraUtter

So this objectID field that it was forcing me to require in the form was an extra ObjectID field that was leftover from a join of two tables. When I deleted it, the form no longer required it. I don't think anything about this situation makes sense or is right, but at least I got it figured out on my end to a point where I can build the forms for my field crews.

All comments

KaraUtter

Thanks, Craig!

cgillgrass

Hi @KaraUtter yes, that would be the reason you ran into this issue. The problem appears to be with the Join itself and preserving the Allow Nulls property for the ObjectID fields after the join. These should be excluded, this isn't an issue in Field Maps but in the app that you performed the Join in, I'll reach out to the Pro team to see if they can address this.

Craig

KaraUtter

I ran a join and then exported the layer with the join so that it would just be a single layer with attribute table. I did this in ArcGIS Pro.

cgillgrass

Hi @KaraUtter how did you perform the join? Was it in Online or Pro or somewhere else?

KaraUtter

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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