It would be nice if bit fields created through target design could be set to default to 0 so the NULL option does not exist. If you manually do this in SQL and then rebuild the table in automate then it removes the default you setup in SQL.
The problem that this created is that all update rules don't work on bit fields now because we always add where field is null. So all bit fields can not longer be updated by an automated rule.
The problem that this created is that all update rules don't work on bit fields now because we always add where field is null. So all bit fields can not longer be updated by an automated rule.
Attachments Open full size