Setting required fields for a feature service in ArcGIS Online

[JoshWhite]

I am testing out a feature service for use in web editing, primarily through Collector.  I am testing in ArcGIS Online.  I tried to edit an existing feature and there are a couple of fields that have a yellow triangle and with an exclamation point next to them and a popup that states that this value is required.  I cannot seem to figure out how this property is set.  The two fields in one particular feature that are marked as required aren't really required and other fields that should be required are not required.  How do I change the property of this?  In the feature class it seems the only thing you could change is whether or not a field is nullable but that doesn't appear to affect anything else.  The template doesn't have an option for requiring fields either.  ArcGIS Online nor Collector have any options that I can find to alter this either.  The service properties don't reference required fields either.

[Anonymous User]

An enhancement request has been logged for this: http://support.esri.com/en/bugs/nimbus/role/beta10_1/TklNMTAzMzk5

This issue has been fixed in Collector for ArcGIS version 10.2.4! Hopefully this is helpful. If this issue is still happening at version 10.2.4 for anyone, let us know - get in touch with Esri Support and we can take a look at it

[JoshWhite]

Julia,

My original problem was really the opposite of that and yes some of the issues are likely resolved for me in 10.2.4.  I want the ability to require fields have a value regardless of whether they are nullable. Others have mentioned domain fields.  Sometimes these would be required, sometimes not, depends on the feature.

[Anonymous User]

Hey Josh -

I see, so currently the workflow is that the yellow exclamation marks will appear if no value is entered in a field and the field is set to non-Nullable. You would like the option to have those yellow warnings appear even if the field is nullable, is that right? With our products, setting a field to be nullable/non-nullable is the property you use to set the field requirements. Granted, there are a few bugs out there for our APIs (ArcGIS Online, Collector iOS, Collector Android) but the theory is:

NULLABLE = "not required"

NON-NULLABLE = "required"

We are actively working on the issues surrounding this particular setting (i.e. enforcing the setting in the APIs), but that's the gist of it.

[NickHetrick]

It was showing up in any field with a domain value which was confusing users. Also the ability to change the attribute for a column that the editing template uses to symbolize is also an issue which then clears out fields that do not have a default value. This behavior does not exist in Arcmap, ArcGIS mobile so it is very confusing to users.

[Anonymous User]

Yes, the issue with all the domain fields was a bug that was fixed. Check out "Collector for ArcGIS 10.2.7 Updated" and specifically NIM103404 on this site: Collector for ArcGIS 10.2.7 Updated! | ArcGIS Blog . I'm not sure I understand what you mean when you say the ability to "change the attribute for a column that the editing template uses to symbolize". Can you explain what you mean by that?

[JoshWhite]

The problem is it that it is difficult to change whether a field is nullable or not after the fact.  I would rather have the ability to control this through the app.  Of course, if a field is non-nullable then that would override any settings in the app until the field could be changed.

[NickHetrick]

I totally agree having this functionality as configurable within the web would be the optimal solution. Having to change items on the backend within the database is much less flexible especially when services are being consumed by multiple application.

[Anonymous User]

Josh - yeah I can see how changing the required/nullable settings on the app itself would be helpful. I recommend posting about it on our ideas page if it's not there already so the Esri Development team can see that you and other users are interested in seeing this functionality.

[ANRGIS]

I posted a similar idea today:

ArcGIS Idea - Collector - Independently select fields as required.

[JoshWhite]

ANR,

That link doesn't seem to work correctly.  It requires a separate log on that isn't the same as the Esri Global ID.