|
Home > Archive > BizTalk Server Orchestration > March 2005 > datetime values...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
datetime values...
|
|
| biztalker 2005-03-07, 5:49 pm |
| Hello,
When my orchestration exposed as a web service receives a document through
from an external source, the values for the datetime fields get changed, i.e.
I end up getting a time that is 1 hour behind the system time (though the
client system is located in the same time zone as us, and they send us the
"correct" time, not offset by an hour). Also, for whatever value I receive
from the client (which they send in the YYYY-MM-DDTHH:MM:SS format), the
microseconds and the -05:00:00 offset always gets appended on our side. How
do I stop this?
1973-04-19T00:00:00.0000000-04:00
| |
| Joerg Fischer 2005-03-13, 5:49 pm |
| Hi,
When you use dstinguished fields, BizTalk is "normalizing" the datetime
value to GMT. Background: the .NET DateTime class does not hold the timezone
information.
You can convert the DateTime value to your local time zone using the
functionality of the DateTime .NET class.
Sincerely
Joerg Fischer
"biztalker" <biztalker@discussions.microsoft.com> wrote in message
news:78874510-E550-4591-858B-FD7185B1A8D1@microsoft.com...
> Hello,
>
> When my orchestration exposed as a web service receives a document through
> from an external source, the values for the datetime fields get changed,
i.e.
> I end up getting a time that is 1 hour behind the system time (though the
> client system is located in the same time zone as us, and they send us the
> "correct" time, not offset by an hour). Also, for whatever value I receive
> from the client (which they send in the YYYY-MM-DDTHH:MM:SS format), the
> microseconds and the -05:00:00 offset always gets appended on our side.
How
> do I stop this?
>
> 1973-04-19T00:00:00.0000000-04:00
|
|
|
|
|