Hi Fred,

Thanks for the response, what we actually have is something like this in 
response and Remedy was not able to capture it.  The repeating info is actually 
the tns:number and it is part of the fields.

<?xml version='1.0' encoding='utf-8'?> <senv:Envelope xmlns:tns="sample" 
xmlns:senv="http://schemas.xmlsoap.org/soap/envelope/";> <senv:Body> 
<tns:searchResponse> <tns:searchResult> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505140</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505141</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505142</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505143</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505144</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505145</tns:number> </tns:DDI> <tns:DDI>
 <tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505146</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505147</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505148</tns:number> </tns:DDI> <tns:DDI> 
<tns:org_code>2093</tns:org_code> <tns:ddi_type>VoIP</tns:ddi_type> 
<tns:number>6445505149</tns:number> </tns:DDI> </tns:searchResult> 
</tns:searchResponse> </senv:Body> </senv:Envelope> 


On Friday, 7 November 2014, 12:52, "Grooms, Frederick W" 
<[email protected]> wrote:
 


** 
Yes
 
Part of it depends on how the 3rd party application defines the response.  As 
long as they define it using a sequence it should work.  You map a child/sub 
form to the repeating info
 
Here is an example
   <xs:complexType name="myComplexResponseType">
     <xs:sequence>
       <xs:element minOccurs="0" name="Field_1"      type="xs:string" />
       <xs:element minOccurs="0" name="Field_2"      type="xs:string" />
       <xs:element minOccurs="0" name="Field_3"      type="xs:string" />
       <xs:element minOccurs="0" name="Attachments"  
type="AttachmentArray_Type"/>
     </xs:sequence>
   </xs:complexType>
 
   <xs:complexType name="AttachmentArray_Type">
     <xs:sequence>
      <xs:element minOccurs="0" maxOccurs="unbounded" name="Attachment_Item" 
type="Attachment_Type" />
     </xs:sequence>
   </xs:complexType>
 
   <xs:complexType name="Attachment_Type">
     <xs:sequence>
      <xs:element                name="AttachmentID"            
type="xs:string"   default="00000" />
      <xs:element minOccurs="0"  name="Attachment_Data"         
type="xs:base64Binary" />
      <xs:element minOccurs="0"  name="Attachment_Name"         
type="xs:string" />
      <xs:element minOccurs="0"  name="Attachment_OrigSize"     type="xs:int" />
     </xs:sequence>
   </xs:complexType>
 
This will generate something like
<ROOT>
   <Field_1>  </Field_1>
   <Field_2>  </Field_2>
   <Field_3>  </Field_3>
   <Attachments>
            <Attachment_Item>
                <AttachmentID>          </AttachmentID>
                <Attachment_Data>       </Attachment_Data>
                <Attachment_Name>       </Attachment_Name>
                <Attachment_OrigSize>   </Attachment_OrigSize>
            </Attachment_Item>
            <Attachment_Item>
                <AttachmentID>          </AttachmentID>
                <Attachment_Data>       </Attachment_Data>
                <Attachment_Name>       </Attachment_Name>
                <Attachment_OrigSize>   </Attachment_OrigSize>
            </Attachment_Item>
            <Attachment_Item>
                <AttachmentID>          </AttachmentID>
                <Attachment_Data>       </Attachment_Data>
               <Attachment_Name>       </Attachment_Name>
               <Attachment_OrigSize>   </Attachment_OrigSize>
            </Attachment_Item>
   </Attachments>
</ROOT>
 
Here in a Filter Set Fields mapping you would map Attachment_Item to a 
child/sub form (somewhat like the order and order line item example in the docs)
 
Fred
 
 
From:Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Wesley Reyes
Sent: Thursday, November 06, 2014 3:35 PM
To: [email protected]
Subject: Multiple Result in a Web Service Call
 
** 
Hi,
 
Would like to ask if Remedy can handle multiple result in a single web service 
call response to a 3rd party application?
 
I set up a set-fields in Remedy that will do a web service call to a 3rd party 
application.  But the application will return multiple result on that since it 
is a wild card query.  Can Remedy able to handle that? if can how should I 
configure my web service to do that.
 
 
Thanks :)
 
 
_ARSlist: "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"

Reply via email to