You need to sign in to do that
Don't have an account?
Superfell
resolution for datetime parsing issues with .NET 2.0
There's been multiple threads on this, I've been working with the Microsoft folks to chase this one down. This is the feeback i got from them.
I tried out the hotfix on the failing test case i had and it addressed the issue, so if you're seeing this problem, you can either call Microsoft PSS and get the hotfix, or if you don't need access to any of the xsd:date fields, you can modify the wsdl by hand to remove these elements, and re-import it, and everything should be good.
If a schema contains both “xsd:date” with nillable=true and “xsd:dateTime” with nillable=true, we will import either both as “date” or both as “dateTime”. In your case, both probably get imported as “date”, hence the time component cases a failure. This is a known bug and there is a hotfix available (KB 925272), available by calling PSS.
I tried out the hotfix on the failing test case i had and it addressed the issue, so if you're seeing this problem, you can either call Microsoft PSS and get the hotfix, or if you don't need access to any of the xsd:date fields, you can modify the wsdl by hand to remove these elements, and re-import it, and everything should be good.
All Answers
I have been struggling with this issue for over a week. Initially, I thought it was related to globalization and date/time format because it was working on our local development server in Australia but not when we pushed it to production in the US.
Turns out it was probably related to the different versions of .NET we are running (we don't have a great deal of visibility to the production server).
I edited the WSDL to always use dateTime and works a charm!
Thanks,
Aaron
Thanks
Kunlun
I ran into this issue as well. The hotfix seems to talk about Windows Vista, but I am running on XP. Does that still apply?
I also tried commenting out this line from the WSDL
<!-- <enumeration value="xsd:date"/>-->
Is that correct?
Thank you,
Chris
I just would like to confirm I was having the same issue here. I was trying to update a date field (custom field) using web services from C# .NET 2.0. It wasn't working and after changing the wsdl it works just fine.
Thanks a lot for the tip.