Feature Service- required fields

6990
11
04-19-2013 04:54 AM
AaronWorthley1
Occasional Contributor II
Is it possible to make some attribute fields in a hosted feature service required?  Ideally I'd like to make this change to an already published service.
Tags (2)
0 Kudos
11 Replies
MikeMinami
Esri Notable Contributor
No. there is no way that I know of to do this. It's a good idea though.

Thanks,

Mike
0 Kudos
AaronWorthley1
Occasional Contributor II
After some testing, it would appear that required fields (Null values not allowed) in a template feature class are not even honored when publishing as a hosted feature service.
0 Kudos
MikeMinami
Esri Notable Contributor
No, there is nothing in the user experience that will test for null values, based on the field setting from the geodatabase that passed to the hosted feature service.  However, as I understand it (I didn't test this), the database may reject creating a feature where fields have null values, but are set as not nullable. However, again, the user experience wouldn't trap any error and provide any user friendly interaction. My guess is (if this is in fact true) that the feature just wouldn't show up and the user would be left wondering what happened. This is just the state of where we are right now...

Thanks,

Mike
0 Kudos
JoshWhite
Regular Contributor III

Mike,

This really needs to be a part of Collector.  We need to be able to customize the experience to make this app the best.  I typically use a Trimble for GPS collection and the software allows me to determine which fields are required and which are not.  Of course this is independent of SDE but I would think that whether or not a field is nullable should have nothing to do with whether or not it is required in Collector.  Of course, if a field in SDE does not allow null values then I could understand why this could be an issue not to require an entry.  In that case, a default value could be created to keep this from being an issue.  Just my two cents on the issue.

Josh White, AICP
Principal Planner

City of Arkansas City
MikeMinami
Esri Notable Contributor

Yes, I agree that Collector should handle this better. Actually, all clients that edit the data should handle this. The only suggestion I have is that when you define the feature templates, you can specify a default value for required fields. At least then it would have a value.

In general, this is an area we're continuing to work on and it will get better.

Mike

ANRGIS
by
Occasional Contributor
0 Kudos
KATIEATKINSON
New Contributor III

I am using my Enterprise Database so I can have domains. I am trying to publish a collector app however when it publishes is comes in empty and says it can not submit. What is the best format to have a collector apps data that allows domains. the File Geodatabase or the Enterprise Database.

0 Kudos
VenusScott
Occasional Contributor III

I use our Enterprise SDE with domains with no issues. The only difference I've found is in the Android vs. iOS. In the Android it goes from field to field as expected, in the iOS it skips the fields with domains and you have to go back to them to fill them out. Annoying...

Disclaimer:

Have not tried this offline. Have not tried this recently either.

0 Kudos
RickeyFight
MVP Regular Contributor

Mike Minami‌ Is there a way to do this now? 

0 Kudos