Hi MolallaComm,

The "enableUTCDates" property is not inside the 12.1 Volume Release. However it will be in the next 12.1 Service Release (8th June).

The reason you're seeing it inside the documentation for 12.1 is a mixup in the documentation generation. As i mentioned the "enableUTCDates" is going to be in the next SR and documentation just got updated prematurely.

Thanks for pointing that out! Sorry for the confusion this may have caused.

Ivan Kosharov

Hi there, after upgrading to 12.1 and removed the formatting function my dates are now being displayed correctly. Looks like something did change when the JSON date strings are parsed from version 11.1 and 11.2?

Thanks again.

Actually, in looking at the 2012.1 documentation, it appears that there is an "enableUTCDates" property on the grid that might be the ticket on this problem, but unfortunately I don't think it currently is wired up to do anything.  Can someone from Infragistics confirm or deny this???

I have to agree with Christoff here.  I'm using 2012.1 latest greatest with oData and the DateTime columns in the database are local times, but when they get sent via JSON the WCF Data Service layer unfortunately converts them into UTC (if I recall, this is a feature of microsoft's json routines in general - if you use JSON.net instead it isn't an issue but unfortunately WCF Data Services are hard wired to use microsoft's own JSON routines).

it is easy enough to write a custom formatter, but it would be nice if we didn't have to as then things would just work out of the box.  How about just adding a new format option called "dateTimeUTC" or something to signify that the underlying datasource is providing the time in UTC format even though we want to display it in local time format?