Because of the way ANM 2026 uses Entities to store the values to be displayed when the Add page first appears, when there is no Default Value set in the UI for a NOT NULL database field, the Entity cannot store that possibility, so it is converted to a type-specific default value (0 for numbers, 1/1/1 for dates, blank for varchar, etc.). This works well for text fields but not as well for numbers and badly for dates. It eliminates the possibility to require the user to enter a date before adding a record: the default value is now a date so it will save an incorrect date if the user doesn't type anything, while previous versions would show the user an error for a required field, which is much better to ensure data integrity. For numbers, depending on where you click in the field you might need to delete the 0 before typing the correct number, and like dates it allows saving the default 0 rather than requiring the user to type something.
What would be a good way to handle this, or am I missing something obvious? Changing the database to allow NULL would be bad database design when the field is actually required. We set the default to CurrentDate() for some databases, but there are some where the current date is almost certainly not the correct value and I feel like that makes it too easy to skip. I suppose I could use Client Script to delete the text in the field from the browser when the page loads, though that would mark the field as changed. I'm not sure if that would cause issues with trying to save blank rows in grid add, it may be an issue regardless because of the default value (even though there is no default value specified). I don't think it would be possible to clear the field using a server event because the Entity actually cannot store a NULL value. I tried manually editing the project file, changing FldAttribute="4" to FldAttribute="36" (adding 32, probably a bit field) to tell ANM the DB field is nullable. That does work, but every time I resync (like when opening the project) it wants to change it back. I think the user gets a different message if they save without filling out the field: an error from the database about NULL instead of ANM field required message, but it maintains integrity, saves when it should and doesn't save when it shouldn't.