Use SubForm Set for a choice in XML Schema

Question

I have questions on subformset, the parameter to the 'setInstances' method and the use of 'intial' attribute of 'occur' element of XFA. <br /><br />In XML schema, sometimes there are exclusive choice. In my example, user has to choose between a customer number and postal-address (name, address, city, state...). I use a check box in the form, so either the customer number or postal address subform can be shown, but not both at the same time. I have no problem displaying them on the form. The problem is when I export the XML data from it. It does not work after user clicks on the check box once. If I use button instead of check box, user can press the button no more than twice. Then only the data of the first element in posta-address are exported.<br /><br />I use setInstances(1) and setInstance(0), but I could not find any documentation on the description of the parameter of setInstances.<br />Anyone can take a look at it and help?<br /><br />Thanks. <br /><br />Hongwei Li<br /><br />I would like to post the XDP file. But it is too long (1000 lines) to fit here. So I post javascript and the XML Schema.<br />==========================================================================<br /><event activity="change"><br />                     <script contentType="application/x-javascript">if(this.rawValue==true){<br /><br />_customerNumber.setInstances(1);<br />_correspondenceAddress.setInstances(0);<br />}<br />else{<br /><br />_customerNumber.setInstances(0);<br />_correspondenceAddress.setInstances(1);<br />}</script>   <br /><br />          <br /><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" id="XFASchemaXSD3"><br />   <xsd:element name="us-correspondence-address"><br />      <xsd:complexType><br />         <xsd:choice><br />            <xsd:sequence><br />               <xsd:element ref="name-1"/><br />               <xsd:element ref="name-2" minOccurs="0"/><br />               <xsd:element ref="us-postal-address"/><br />            </xsd:sequence><br />            <xsd:element ref="customer-number"/><br />         </xsd:choice><br />      </xsd:complexType><br />   </xsd:element><br />   <xsd:element name="name-1" type="xsd:string"/><br />   <xsd:element name="name-2" type="xsd:string"/><br />   <xsd:element name="us-postal-address"><br />      <xsd:complexType><br />         <xsd:sequence><br />            <xsd:element ref="address-1"/><br />            <xsd:element ref="address-2" minOccurs="0"/><br />            <xsd:element ref="city"/><br />            <xsd:element ref="state" minOccurs="0"/><br />            <xsd:element ref="postcode" minOccurs="0"/><br />            <xsd:element ref="country"/><br />            <xsd:element ref="email" minOccurs="0" maxOccurs="unbounded"/><br />            <xsd:element ref="phone" minOccurs="0" maxOccurs="unbounded"/><br />            <xsd:element ref="fax" minOccurs="0" maxOccurs="unbounded"/><br />         </xsd:sequence><br />      </xsd:complexType><br />   </xsd:element><br />   <xsd:element name="customer-number" type="xsd:string"/><br />   <xsd:element name="address-1" type="xsd:string"/><br />   <xsd:element name="address-2" type="xsd:string"/><br />   <xsd:element name="city" type="xsd:string"/><br />   <xsd:element name="state" type="xsd:string"/><br />   <xsd:element name="postcode" type="xsd:string"/><br />   <xsd:element name="country" type="xsd:string"/><br />   <xsd:element name="email" type="xsd:string"/><br />   <xsd:element name="phone" type="xsd:string"/><br />   <xsd:element name="fax" type="xsd:string"/><br /></xsd:schema>

Answer 1

Jimmy,
Sorry about the negligence. Thanks a lot!
This time I can not even export the data of member number for once. Actually I tried different hierarchies (the default by designer is using subformset and useoneof, I have to make changes in XDP to mark both of the min attribute to '0' and one of the branch intitial attribute of occur element to '1'). I had no no luck.
I think this is an Acrobat 7.0 bug. Or in another word, Acrobat 7.0 is not ready to handle XML schema when the content model is more complex. I will have to wait until we go documentation on setInstances() method. I guess the reason of the bug (if it is) is because when you do the setInstances(0), the branch of data DOM was set to NULLType and could not recover back when you click the checkbox to reactivate this portion again.
Hongwei li