Fred,

my Priority field is a Character Field. When I consume their web
service the say that their priority field is a

<xsd:element name="PRIORITY" nillable="true" minOccurs="0">
                              <xsd:simpleType>
                                <xsd:restriction>
                                  <xsd:simpleType>
                                    <xsd:restriction
base="xsd:string">
                                      <xsd:whiteSpace
value="preserve"/

                                   </xsd:restriction>
                                  </xsd:simpleType>
                                  <xsd:enumeration value=""/>
                                  <xsd:enumeration value="1"/>
                                  <xsd:enumeration value="2"/>
                                  <xsd:enumeration value="3"/>
                                  <xsd:enumeration value="4"/>
                                  <xsd:enumeration value="5"/>
                                </xsd:restriction>
                              </xsd:simpleType>
                            </xsd:element>

I did try to set my priority field by hand to numbers (1, 2, 3, 4, 5)
and to characters (Low, Medium, High etc.). None of the worked. I
might try to re-create my priority field to an enumeration field, but
since their data type is xsd:string I wonder if it does make any
sense.

When I change

<xsd:element name="PRIORITY" nillable="true" minOccurs="0">
                              <xsd:simpleType>
                                <xsd:restriction>
                                  <xsd:simpleType>
                                    <xsd:restriction
base="xsd:string">
                                      <xsd:whiteSpace
value="preserve"/




                                    </xsd:restriction>
                                  </xsd:simpleType>
                                  <xsd:enumeration value=""/>
                                  <xsd:enumeration value="1"/>
                                  <xsd:enumeration value="2"/>
                                  <xsd:enumeration value="3"/>
                                  <xsd:enumeration value="4"/>
                                  <xsd:enumeration value="5"/>
                                </xsd:restriction>
                              </xsd:simpleType>
                            </xsd:element>

to

<xsd:element name="PRIORITY" nillable="true" type="xsd:string"
minOccurs="0"/>

before re-loading their WSDL then I will have to re-map all fields,
because the Reload in the Dev Studio destroys all maping each and
every time.


Thanks
Mark



On 28 Feb., 22:49, "Grooms, Frederick W" <[email protected]>
wrote:
> When you map to an ARS Selection field (Selection List, Check box, or Radio 
> Button) the Web Service wants the displayed string value and not the numeric 
> value.  i.e.  If the Values are Low, Medium, and High (number values = 0, 1, 
> 2) you need to pass the text (Low, Medium, and High) and not 0,1,2.
>
> Try this ... Create a plain Character Display Only field to hold the mapped 
> in value and then use a Remedy filter to set the actual Priority value (Since 
> you are passing numbers as a string you may have to have the filter set a 
> Display Only integer field first then set Priority from the integer).  You 
> should not have to remap the entire XML, only change the one field mapping.
>
> Fred
>
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList) 
> [mailto:[email protected]] On Behalf Of Mark Milke
> Sent: Monday, February 28, 2011 3:28 PM
> To: [email protected]
> Subject: Re: ARERR [8959] The XML data type is not supported. <>
>
> I think I'm one strep further. I've discovered that the error occurs
> only when I set the priority field during the consumption of the Web
> Service.
>
> Their WSDL looks here like this:
>
> <xsd:element name="PRIORITY" nillable="true" minOccurs="0">
>                               <xsd:simpleType>
>                                 <xsd:restriction>
>                                   <xsd:simpleType>
>                                     <xsd:restriction
> base="xsd:string">
>                                       <xsd:whiteSpace value="preserve"/
>
>                                     </xsd:restriction>
>                                   </xsd:simpleType>
>                                   <xsd:enumeration value=""/>
>                                   <xsd:enumeration value="1"/>
>                                   <xsd:enumeration value="2"/>
>                                   <xsd:enumeration value="3"/>
>                                   <xsd:enumeration value="4"/>
>                                   <xsd:enumeration value="5"/>
>                                 </xsd:restriction>
>                               </xsd:simpleType>
>                             </xsd:element>
>
> Does this fall within Limitations of ARS?
>
> Well, when I leave the field empty, it's working fine. When I set it
> to 1, 2, 3, 4 or 5 I get the error.
>
> I guess I would have to change their WSDL to:
> <xsd:element name="PRIORITY" nillable="true" type="xsd:string"
> minOccurs="0"/>
>
> the he would let me go, but than I would again have map hundred fields
> by hand in the fancy developer studio.
>
> Mark
>
> ___________________________________________________________________________­____
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> attend wwrug11www.wwrug.comARSList: "Where the Answers Are"- Zitierten Text 
> ausblenden -
>
> - Zitierten Text anzeigen -

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to