- General Development
- Schema Development
- Apex Code Development
- Visualforce Development
- Formulas & Validation Rules
- Force.com Sites & Site.com
- Chatter Development
- Java Development
- .NET Development
- Perl, PHP, Python & Ruby
- Desktop Integration
- APIs and Integrations
- Visual Workflow
- Apple, Mac and OS X
- VB and Office Development
- AppExchange Directory & Packaging
- Salesforce Labs & Open Source Projects
- Other Salesforce Applications
- Jobs Board
11-03-2006 04:46 PM
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.
Solved! Go to Solution.
04-17-2007 12:07 AM
04-24-2007 11:02 AM
02-07-2008 03:32 PM
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!
12-28-2008 05:01 AM
06-03-2009 04:28 AM
08-25-2009 01:10 PM - edited 08-25-2009 02:28 PM
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?
08-18-2010 02:18 PM
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.