AnsweredAssumed Answered

4.14 date and number field validation broken

Question asked by stacy.rendall on Feb 5, 2020
Latest reply on Feb 16, 2020 by stacy.rendall

Editing Date fields through either FeatureForm or Editor widget is broken because the API treats a null value as valid date/number, even if the field is specified as required and has a RangeDomain. Docs: FieldConfig | ArcGIS API for JavaScript 4.14 


This means that when creating a new feature the user can just "click through" date/number fields without entering anything (recorded as a null) (or if editing, deleting the existing values) and the API will accept this null value as valid.


Should FieldConfig support a nullable (boolean) option?