Force users to enter values for NOT NULL attributes

[Vincent828]

ArcGIS Pro should enforce NOT NULL attributes in the application, which then forces the user to input a value to satisfy the constraint.

Currently, there’s no user experience in ArcGIS which enforces this contract when attributes are defined as NOT NULL – when a value is not set the value defaults to an empty string or integer. This is invalid behavior and the work arounds are not suitable, using contingent attribute values or an attribute rule to raise an error. This enhancement begins with the application UX to require the user to set a value before applying the edit.

[SSWoodward]

I just want to make sure I'm understanding you correctly.  Can this idea be summarized like below?

When a field does not allow nulls, raise an error when a user tries to enter a feature with a null value in that field instead of defaulting the value to a non-null value.

[SSWoodward]

Thank you for this Idea. 

Changing the behavior of non-nullable fields is not currently up for consideration. 

This change would be a breaking change to numerous workflows. Non-Nullable fields ensure that fields do not contain a true null value and are not a proxy for marking input to a field as required. When no value is provided for a non-nullable field, a system default value of an empty string, zero, or date equivalent of zero will be be written to the value to ensure no true Null values are present in the field.