It all depend on your xsd definition. An example her: nillable vs minorrours
http://www.dimuthu.org/blog/2008/08/18/xml-schema-nillabletrue-vs-minoccurs0/comment-page-1/ -- J 2014-09-24 13:47 GMT+02:00 Misi Mladoniczky <[email protected]>: > Hi Jarl, > > Are you sure that the element will be skipped if it is set to NULL? > > I think that a NULL value is still considered a value in Remedy. There is > no > way to skip it if you include it in the attribute list. > > Best Regards - Misi, RRR AB, http://rrr.se > > > Agree that the WSDl should support NULL values, which is a value. > > > > It could be that the xsd is wrong. If it contains information that the > > element is required, BMC Remedy always sends the element, regardsless if > > its empty or not. > > > > -- > > J > > > > 2014-09-24 12:20 GMT+02:00 Misi Mladoniczky <[email protected]>: > > > >> Hi, > >> > >> I have seen this a few times. I think it is the standard Microsoft > >> implementation that does not handle NULL values, for example for > numbers. > >> > >> Could it be possible to send a 0 (zero) instead of NULL in these cases? > If > >> you > >> can do that it is a single filter per field, and possibly the need to > >> create > >> display-only placeholders for the value. > >> > >> You could also create different filters for each possible combination of > >> NULL/non-null values, but this could become too much if you have more > than > >> 2-3 > >> fields. > >> > >> Or you might persuade your WebService supplier to support NULL values... > >> > >> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP > 2011) > >> > >> Ask the Remedy Licensing Experts (Best R.O.I. Award at > WWRUG10/11/12/13): > >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. > >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy > logs. > >> Find these products, and many free tools and utilities, at > http://rrr.se. > >> > >> > We're trying to consume an external, non-Remedy web service, using a > set > >> field > >> > from web service filter action. Watching arpluginsvr.log I can see the > >> > transaction successfully reach the vendor system, but it's erroring > out > >> due to > >> > failing validation on the other side. The XML being passed by the > plugin > >> > server is the entire WSDL - the vendor indicates that we need to pass > >> only > >> > those elements that contain an entry - no null values. > >> > > >> > The WSDL location points to the vendor's published WSDL, not a locally > >> saved > >> > file. Even if we were able to use modified WSDL entries stored > locally - > >> we're > >> > not as basic authentication is needed - the values being passed are > >> obviously > >> > going to vary from transaction to transaction. What I'm hoping to > learn, > >> is if > >> > there is any way to vary the values being passed by the plugin server > so > >> as to > >> > eliminate nulls, while using a single WSDL. > >> > > >> > TIA > >> > > >> > > >> > _______________________________________________________________________________ > >> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > >> > "Where the Answers Are, and have been for 20 years" > >> > > >> > >> > >> > _______________________________________________________________________________ > >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > >> "Where the Answers Are, and have been for 20 years" > >> > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > "Where the Answers Are, and have been for 20 years" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
