Webservice provider with nullable datetime: please follow standard behaviour!

By Robert Chanphakeo on 2 Jan 2012
In the latest update outsystems improved web service reference, which now allows for nulliable datetime. (See below)

However it does not allow for nullable datetime for web service providers, that means
nulldate in a SOAP web service response will return 
1900-01-01T00:00:00. rather than an empty element.

Please fix the web service provider null date time issue with the standard nulliable date behaviour (ie Have an option not to include the nulldate as 1900-01-01T00:00:00 but rather an empty element)
"XML Schema: Structures introduces a mechanism for signaling that an element should be accepted as ·valid· when it has no content despite a content type which does not require or even necessarily allow empty content. An element may be ·valid· without content if it has the attribute xsi:nil with the value true. An element so labeled must be empty, but can carry attributes if permitted by the corresponding complex type."


Service Studio (2011-11-19) 

What's new in 

o Web Reference enhancements: 

? Support for Null and Nillable parameters and attributes (#253956) 

This can be seen in the image below

REF: http://www.outsystems.com/help/servicestudio/6.0/Designing_Actions/Input_Parameter_Properties.htm
Kilian Hekhuis5 Jan 2012
This seems more of a bug to me than anything else. Have you reported it to OutSystems support?
Remco Dekkinga20 Aug 2015
In version 9 all the options they created here are removed. It is now impossible to set a field to optional / mandatory.
See the manual: https://www.outsystems.com/help/servicestudio/9.0/Integrating_with_other_systems/Web_Services/OutSystems_Data_Types_to_XML_Data_Types.htm

I would like to see that Outsystems fixes the SOAP Webservices with the default behavior.