I am trying to make a simple Web Service task, but seems like I am having trouble sending null values. Please see the images below, that is how I have setup the LookupRequest and how the query should look like.





With that request I get the following error from the Web Service:

One and only one of the fields DomainName and DomainNumber must be set

So seems like VisualCron is sending the DomainName field even though I have set it to null?

Is there also any way to debug this? For example see the actual payload sent to the Web Service?

Could you add some screenshots of settings of that value? Which version of VC are you running now?

---

Could you add some screenshots of settings of that value? Which version of VC are you running now?

In VisualCron:



In the WSDL:



Is this what you wanted? We are using VisualCron 7.1.6.

Thanks, we will try to set up a web service and test this and get back to you next week.

---

We did some tests and this seems to be the way null strings are serialized when using web service requests. We got the same result when manually calling a web service with a string object with value null. It is transformed to string.empty when received.

---

We did some tests and this seems to be the way null strings are serialized when using web service requests. We got the same result when manually calling a web service with a string object with value null. It is transformed to string.empty when received.

So basically the actual request does not send <DomainName xsi:nil="true"/> but <DomainName></DomainName> instead and this is picked by the Web Service since null != empty? Is there any workaround for this?

We did some tests and this seems to be the way null strings are serialized when using web service requests. We got the same result when manually calling a web service with a string object with value null. It is transformed to string.empty when received.

So basically the actual request does not send <DomainName xsi:nil="true"/> but <DomainName></DomainName> instead and this is picked by the Web Service since null != empty? Is there any workaround for this?

The best workaround is to change the behavior at server level as the other part is out of control.

---

The best workaround is to change the behavior at server level as the other part is out of control.

Thanks for your input, I have forwarded this to our Web Service vendor.

We did some tests and this seems to be the way null strings are serialized when using web service requests. We got the same result when manually calling a web service with a string object with value null. It is transformed to string.empty when received.

So basically the actual request does not send <DomainName xsi:nil="true"/> but <DomainName></DomainName> instead and this is picked by the Web Service since null != empty? Is there any workaround for this?

The best workaround is to change the behavior at server level as the other part is out of control.

I contacted the vendor and they had good reasons for not changing the implementations. But they very much said that this should work as is in the current .Net Web Service classes. Here is one quote:

The standard webservice framework in .Net correctly sends xsi:nil=true for fields that are set to null in the call.

I also kind of understood that it should be like this, since you have the "Is Null" checkmark. So if this checkmark is on, you should xsi:nil="true" instead of empty value?