Add |
Note |
---|
The hour portion of this value is over-ridden by the StartTime property plus the HoursPerDay. |
Caution |
---|
Specifically regarding this property it is very important that when sending in DateTime data that you do not send in the time zone offset from your server such as:
- Date(1437433200000+02:00) - 2015-07-31T07:00:00.00+02:00 Where the time zone offset is the last portion of the DateTime object "+02:00". The input value should be a RAW DateTime value such as "2015-07-31T07:00:00.00". Be sure to follow the specifications of your programming language for turning off time zone offsets when sending in the DateTime. If you are using SOAP and unsure of the incoming format that may be applied by your generated proxy layer then please use a tool like fiddler to inspect your outgoing SOAP packets for the format that your proxy service tool may generate. To avoid sending the time zone offset in C# you can specify the following syntax on the DateTime string before sending: C# //Remove timezone offset
DateTime dtNow = DateTime.Now;
newPunch.TransactionDateTime = DateTime.SpecifyKind(dtNow, DateTimeKind.Unspecified); SOAP <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> ... <!-- Any date time value stored in time web services --> <app:InputDate>2016-04-01T00:00:00</app:InputDate> ... </soapenv:Envelope> JSON DATES: When working with JSON date time objects use the epoch time stamp in milliseconds based on UTC time. For example if you provide the value "DateTime":"\/Date(1465459200000)\/", it should be recorded in the database as 2016-06-09 08:00:00.000. This will create an entry in the database as a RAW date time void of any offset. Because the time-web data center servers all run on UTC times this format is required for JSON date times on this specific property. |