Hello DW,
Im in the middle of a upgrade progress from DW8 to DW9 and I found out that you have added some more strict constrains to some columns.
In partically 'bit' are not allowed to be null anymore - at least in some places.
The issue for our solution is that we use the null value indicate no decision has yet been made. For example AccessUserNewsletterAllowed in AccessUser table, we use the null value to indicate that a new user has not yet decided on allowing newsletters.
So false/true and null gives us this flexibility.
And there are some other columns aswell that we utilize in this way.
Do you think your internal code would break if we change these values back to being nullable in the database?
I would assume the short answer is: make a new custom table with custome columns to accommodate this business need. Time is of the essense though, and this upgrade project is already a bit overdue, and if you could say that you changed these to 'not null' just because it is best practice then we would consider changing them.
Thank for the help
Kind regards
Frederik