LS HTML Client, weird Date issue

Question

Here's a strange one... In an application that I've just made, upon saving a record, LS seems to automatically modify the date of the record by exactly minus 1 day (say from 9/17 to 9/16). Now, there is some criteria for this to happen:
1. An value must be modified that has not previously been modified in the record.  An example would be "Temperature", this is a required INT.  If I start a record and leave it at 0, Save, then go back into the record and add a value and
Save, the date on the record is automatically changed back a day.
Here's the kicker... the date change is only visual, the date value in the DB has not changed.  As soon as I hit F5 on my browser the date is correctly updated back to what was originally saved.
The app does not have any events happening in the Updated/Updating/Inserting/Inserted methods.  The date is automatically added in the _Created event for the DB Entity.
(this happens in both debug mode and when published to an Azure website).

Answer 1

Hi!
I've been having the exact same problem and unfortunately the workaround proposed above did not fix the issue or this workaround (from http://stackoverflow.com/questions/28483086/datetime-textbox-in-lightswitch-html-increments-one-hour-on-save/28491688#28491688)
// Open msls-2.5.2.js
// Locate this section of code:
entitySet._loadedEntities[entityData.__metadata.uri] = entity;
} else if (entityState === _EntityState.modified) {
originalEntityData = entityData.__original;
$.each(entityDetails.properties.all(), function (j, property) {
// You need to add:
convertDatesToLocal(changeResponse.data);
// Example:
entitySet._loadedEntities[entityData.__metadata.uri] = entity;
} else if (entityState === _EntityState.modified) {
convertDatesToLocal(changeResponse.data);
originalEntityData = entityData.__original;
$.each(entityDetails.properties.all(), function (j, property) {
// Hope this helps.
One fortunate thing is that the change is only 'visual'.. so I'm okay with it for now although I would love to have a fix for this until I wait for VS 2015.
Thanks,
Mani