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.
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.
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.
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...
Have not tried this offline. Have not tried this recently either.
Retrieving data ...