Able to save new features even if attributes that do not Allow NULL are not given a value
Hello.
So we have an sde setup on SQL where a lot of features do not allow NULL values for a selection of attributes if their respective feature is created, as in if you do not give certain attributes values then the creation does not get saved, you get the error. See an example of a setup here:
This has always worked fine from PRO and Enterprise, until now when it suddenly doesn't any longer as you are now allowed to create and save edits even if you have not filled out attributes that are clearly setup up not to allow NULL values. No error messages and so forth, it just smoothly saves the edits. See an example of recent edits made to the dataset on the screenshot above:
Where I just effortlessly added 3 features and for Creator, GPZ and PM attributes that don't allow NULL then they just get filled out as blank values while Project that does allow NULL gets <Null> .
I have checked the editing options and "Enforce attribute validation" is enabled, the no null values are set when the dataset is created from scratch, and still no luck. And to be clear, all this worked perfectly until recently even though we have no changes to our database setup.
Is this a problem migrating from Pro 2.x to 3.x or what on earth could this be?
