Entity Designer ignores DEFAULT CONSTRAINT on columns in SQL Server by SAinCA

Standard "who" columns typically include a datetime of "when" the change occurred. For multi-time-zone applications, the decision is frequently made to standardize the values relative to a time-zone or UTC, so that if a user on the East Coast of the USA records an update and one on the West Coast updates at the same UTC time, both record the same updated_when datetime value. In my case, the DB server is under EST and Users are anywhere from East to West plus AK and HI, so we use the server-time. Knowing the User's "home" UTC Offset, the data can be displayed in local time when needed.

The problem lies in the fact that according to the DB schema, the "updated_when" column is NOT NULL. It also has a DEFAULT CONSTRAINT of (GETDATE()) to _always_ assign a value. LightSwitch gives NO OPTION but to supply a valid DateTime value for every INSERT and UPDATE. The presence of the DEFAULT CONSTRAINT clearly renders this unnecessary but there is NO facility in LS to override this behavior.

Please modify the Entity Designer so that selected columns can be changed from Mandatory to Optional WHERE A DEFAULT CONSTRAINT EXISTS IN THE DATABASE. Provisions made by the Data Architect/DBA should be recognized by the Designer Tool and overrides permitted.