Want to make some fields required when data is being collected; i.e. should not be able to complete edit ( or Submit) without these fields having data entered
The fields in question do have domains and it looks like that may prevent it being required somehow. The original feature class has "No" in the Allow Null Values property for these fields, but in Collector that may only work for fields without domains?
Hi Dan - thanks for the reply. The fields in question do have domains and it looks like that may prevent it being required somehow. The original feature class has "No" in the Allow Null Values property for the fields of interest , but in Collector that may only work for fields without domains?
Currently there isn't an ESRI designed method for creating required fields. We have brought this up with them several times over the last year and they say it is in the works. In the meantime we have found an option that does work but ESRI tells us is not "by design". It will make the fields required though and the submit button is grayed out until all required fields are populated. Have a write up on this workaround if you want to e-mail me at firstname.lastname@example.org I can pass it along to you. Just understand that at this time ESRI states this is a BUG workaround so something as simple as a future update may break this working or they may decide to use this as the workflow for creating required fields.
Hi Serj, How well does this work for views? When I tried this on an empty file geodatabase (no data) that I had published to AGO using the publish web layer in Pro and created a view and web map, the required fields did get picked up by Collector for a web. But when I created a 2nd view and web map from that 2nd view, the required fields did not work correctly with the date going back to 1899, and 0s in some of the required fields. There was not any data in the feature service. Is this possibly a workflow issue?