Hi Jarl, Yes it does. We tried it both ways after my original post.
As it turned out, NULL-values was OK for character fields but not for Integers and Date Fields. By changing the mapping sligthly for Date and Integer Fields and changing the Properties->Type to string instead of dateTime/integer/double, we could circumvent the problem. The bad thing about that solution was that the data was sent as a string instead of the correct type. The other solution we found, was to use the wsdl.exe from Microsoft to generate code specific to the specified WSDL and programming language. Just google for wsdl.exe, and you will get to the correct page: http://msdn2.microsoft.com/en-us/library/7h3ystb6(VS.71).aspx After the template code has been created, you can go in and change the code for the specific fields so that it works the way you want it to. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. * RRR|Translator - Manage and automate your language translations. Find these products, and many free tools and utilities, at http://rrr.se. > Does the XML schema states that the elements can be null? > > -- > Jarl > > On Dec 19, 2007 9:50 AM, Misi Mladoniczky <[EMAIL PROTECTED]> wrote: >> Hi, >> >> When a NULL-value is returned from the AR System Web Service, the .net >> developer gets the following error. The problematic XML-tag is the empty >> tag <ns0:Integer_Field xsi:type="xsd:int"/>, but it is the same with any >> empty tag/field. >> >> There is an error in XML document (4,41) >> >> 2007-dec-18 11:31:31 - FINE (com.remedy.log.WEBSERVICES) : output >> document >> from AR >> Server: <?xml version="1.0" encoding="windows-1252"?> >> <ns0:ROOT xmlns:ns0="urn:MinSidaWebServiceTest" >> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> >> <ns0:Assigned_To xsi:type="xsd:string">Rolf</ns0:Assigned_To> >> <ns0:Create_Date >> xsi:type="xsd:dateTime">2007-12-13T08:43:06+01:00</ns0:Create_Date> >> <ns0:Integer_Field xsi:type="xsd:int"/> >> <ns0:Last_Modified_By >> xsi:type="xsd:string">MinSida</ns0:Last_Modified_By> >> <ns0:Modified_Date >> xsi:type="xsd:dateTime">2007-12-13T08:43:06+01:00</ns0:Modified_Date> >> <ns0:Request_ID xsi:type="xsd:string">000000000000001</ns0:Request_ID> >> <ns0:Short_Description >> xsi:type="xsd:string">Test</ns0:Short_Description> >> <ns0:Status xsi:type="xsd:string">New</ns0:Status> >> <ns0:Status_History >> xsi:type="xsd:string">2007-12-13T08:43:06+01:00MinSida</ns0:Status_History> >> <ns0:Submitter xsi:type="xsd:string">Ulf</ns0:Submitter> >> </ns0:ROOT> >> >> Any suggestions on what has been done wrong on the .net side? >> >> Best Regards - Misi, RRR AB, http://rrr.se >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
