Unable to pass Nillable fields to .Net Webservices

1
We pass field values to a .Net webservice that can be a nil value. When we pass a string field with the value of "empty" from Mendix, the trace reveals that we are passing the following XML island in our request: <mx:PreagreementStatement><![CDATA[null]]></mx:PreagreementStatement> Obviously this request is invalid on the .Net's webservice. The only values it accepts is a literal 'Y' or 'N' or nil value. The asmx webservice is expecting this in the request: <mx:PreagreementStatement xsi:nil="true"/> Does Mendix cater for this nillable attribute when it generates the webservice request in the mapping, and if so how does one configure this in the mendix domain to xml mapping?
asked
2 answers
1

Some more information regarding this. The asmx webservice is expecting this in the request:

<mx:PreagreementStatement xsi:nil="true"/>

Does Mendix cater for this nillable attribute when it generates the webservice request in the mapping, and if so how does one configure this in the mendix domain to xml mapping?

answered
0

This should work, and an xsi:nil should show up in the webservice call. Would you mind filing a bugreport in the support portal?

answered