Well I tried the minOccurs=0 but it did not seem to make a difference BMC Knowledge base has this: KM-000010027821 Q: Performing a webservice operation (opGet or opGetList) with no matching entries returns an AR 302 error. A: This error is considered "as designed" and was implemented as a result of defect SW00220338.
Thanks, --- John J. Reiser Senior Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me Roger, I read in the documentation that for "Outgoing XML elements . . . If the number of entries in the base form is less than the minOccurs, AR System returns an error." My SWAG on this is if I set the getListValues minOccurs = 0 then a query that returns no records is not less than 0 and should not throw the Error 302. Once I get a chance to try it out I'll pass it on. Thanks, --- John J. Reiser John, Because of the limited functionality that Remedy has regarding web services I do not believe there is a way to 'handle it' on the Remedy side. We have a similar integration in which the group consuming my web service captures the error messages and displays something different to the end users. They do keep a log of the actual error for troubleshooting purposes. Good luck with this. Roger Nall ----------------------------------- Hello Listers, ARS 7.1 Midter 7.1 MS SQL Server 2005 MS Windows 2003 enterprise I have made a web service with Get and GetList for a form. I sent the WSDL to the group that wants to query the form. When they search for a value that returns no records it responds with: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; soapenv:mustUnderstand="1"/> </soapenv:Header> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.userException</faultcode> <faultstring>ERROR (302): Entry does not exist in database; </faultstring> <detail> <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/";>(redacted)</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> In the web page it shows as an error message "Error retrieving tickets". I think they are using something called iView in a portal web site and displaying the ticket information in a few tables. They have asked me to "handle this on the Remedy end" and provide a "No results". I think that since Error 302 is what the ARSystem generates for API/Webservice calls there isn't much that I can do. Shouldn't they be able to trap this error and display whatever text they want? Or is there something I can add to the WSDL to respond with "0 Records" when a query comes up empty? Something in the mapping perhaps? As you can tell I don't speak XML. Thanks in advance for any guidance. --- John J. Reiser _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
