Are these fields defined as Optional (minOccurrs=0) in the Web Service? If you look at the inbound XML you will probably see that (in this example) the Status element does not exist.
Try defining these fields a minOccurrs=1 and Nillable. This way the portal should always place the element name in the XML even if there is no data for that element. See pg 333 in the "Integrating with Plug-ins and Third-Party Products" manual for more info on minOccurrs and Nillable. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of versicle Sent: Thursday, February 07, 2008 5:25 PM To: [email protected] Subject: Re: Multi-qualified Web Service Search Yes. Here is the error I'm receiving when passing a NULL value: ERROR (4558): Qualification line error; Also here is the Qualification: 'Status' = XPATH(/ROOT/Status) Rick Ponzo-2 wrote: > > When you created the web service did you set the data elements value > Nillable = True for each of the fields? > > Rick Ponzo > > > versicle wrote: >> All, >> >> I have created a WS based on the HelpDesk form and we have a business >> requirement from a web Portal to be able to search for tickets based >> on one or MORE of the following fields, Customer Last Name, Ticket >> Number, Company, Status, and Priority. I have created an search >> operation and mapped all of the fields above. However, I only receive >> responses when each of the fields has a value entered for the search >> otherwise an error is returned. Is there a way to have a wildcard in >> the search or a NULL value for one of those fields I dont care about >> when executing the search? >> >> I am running ARS 7.1 patch001 and IM 7.0.03 patch006 on Solaris 10. >> >> Thanks, >> >> Mike >> > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
