Xml Schema xs:choice element in dynamic forms

Hi all,
I'm developing an xml schema for creating the data model of a form. I connect LC Designer-8.2ES to this schema.
In the schema I do have mutually exclusive elements implemented with a <xs:choice> element. A very comparable situation was described in this thread : http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=123 in 2007.
The problem, as related in this thread, is that only the very first element of the choice is displayed in the generated pdf and I don't know how to display all parts as a real choice. So what's the best way to let user fill in one part or the other of the choice?
Does it need to be implemented with scripting (xfa...myform.presence = visible | hidden)?
I want that only the filled element of the choice be exported from the form, the resulting xml being valid according the schema. I seems to work, but as of now, only for the first element...
BTW, what's the best document describing what parts of xml schema are usable in dynamic XFA forms? Is it 100% compatible? I've observed that the constraints in my schema are not validated in the forms. Shouldn't xml schema generate validating script in LCD? Does it apply for a subset of xml schema?
Thanks in advance,
jgrd

Hi all,
finally, I understand that we cannot use "anonymous" sequences neither in LiveCycle (like this following example where person might have many email)
 <xs:element name="person">
 <xs:complexType>
 <xs:sequence maxOccurs="unbounded">
 <xs:element name="email" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
valid instance with 3 emails :
<person xsi:noNamespaceSchemaLocation="Untitled39.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <email>String</email>
 <email>String</email>
 <email>String</email>
</person>
In LC Designer, element with same name (<email>) are not used AFAK. Maybe I'm wrong?
The same hands with <xs:choice> where only first choice appears in pdf although being present in LC Designer.
As for sequences, my idea is to produce <email1>, <email2>, etc. in a static schema, before connecting schema's data to LCD.
Hope someone can show up and tell it's the right way or not.
Regards
jgrd

Similar Messages

Binding XML Schema to Repeating Elements - What am I doing wrong?

I managed to successfully bind a schema to a basic form and aside from some Reader Enabled issues it works as expected.
My next project is to do the same but with a form that features repeating subforms.
I have written my schema and validated and all seems well. When I bind it to the form though it makes certain fields behave in an odd way.
The form is made up of three sections. The first is a single subform of non repeating fields. Parts Two is a table with repeating rows and Part Three is a collection of fields with an Add/Delete button using the instance manager script.
When I bind these fields and add rows I get strange results. In Part Two pressing the Add button copies the entire row rather than creating a new one. Changing the value of one row changes the others.
In Part Three I can create entirely new subforms using the Add button but the this.parent.index +1; script stops working.
Does anyone know why this might be happening and how I can resolve it?
The schema is below:
<xsd:element name = "RemoteWorking">
<xsd:complexType>
<xsd:sequence>
 <xsd:element name = "PartZero">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name = "RequireAddHardWare" />
 <xsd:element name = "RequireRemoteWork" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name = "PartOne">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name = "Surname" />
 <xsd:element name = "FirstName" />
 <xsd:element name = "UserName" />
 <xsd:element name = "JobTitle" />
 <xsd:element name = "Role" />
 <xsd:element name = "LineManager" />
 <xsd:element name = "Directorate" />
 <xsd:element name = "PersonnelCategory" />
 <xsd:element name = "CONumber" />
 <xsd:element name = "TelephoneNumber" />
 <xsd:element name = "BuildingCode" />
 <xsd:element name = "RoomNumber" />
 <xsd:element name = "WorkingHours" />
 <xsd:element name = "AltContact" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name = "PartTwo" maxOccurs = "unbounded">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name = "AdditionalHardware" maxOccurs = "unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name = "PartThree" maxOccurs = "unbounded">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name = "ItemRequired" />
 <xsd:element name = "UserAccountName" />
 <xsd:element name = "CostCentre" />
 <xsd:element name = "BusinessCase" />
 <xsd:element name = "Device" />
 </xsd:sequence>
 <xsd:attribute name="ItemNo" type="xsd:integer" use="required"/>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name = "PartFour">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name = "Unite" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

The binding expressions needs to indicate that you can have more than one PartTwo section. To accomplish this you will need to add a [*] to the binding expressions that use teh PartTwo node. If you want to keep it simply, bind the subform that holds th information for PartTwo to the PartTwo node, then add the [*] to the end of the expression. Then al children of that node will get expressions like $.Name of the Node that it is referencing.
Hope that helps
Paul

XML Schema any element

I have a list of schema files and they a number of elements in them. But for my data extraction i use only close to 300 tags. When i register the schema I get an error that a table cannot of have more than 1000 columns. My work mate is working on Annotations and I am planning to build a new schema to make extract only these 300 tag names and also make sure the XML file can be validated like it did earlier. Explaining this i came across a complex type element called *<any>* which can be used to allow elements to be available which are not declared within the schema file.
My Original schema file looks something like below,
<xsd:complexType name="WfInformation">
<xsd:all minOccurs="0">
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
<xsd:element name="IndependentOffice" type="WfIOffice" minOccurs="0" />
<xsd:element name="AffiliateCompany" type ="WfIAOffice" minOccurs="0" />
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
<xsd:element name="ReferenceID" type="xsd:string" minOccurs="0" />
</xsd:all>
</xsd:complexType>
of the above list of items i use only elements Company, HeadOffice, Number. After reading through some documentation I wanted to <any> tag like below,
<xsd:complexType name="WfInformation">
*<xsd:sequence>*
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*<xsd:any processContents="lax"/>*
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*</xsd:sequence>*
</xsd:complexType>
My question is if I am correcting the lines as i mentioned above will be Register schema again fail with same reason that i have 1000 columns. As i understand every element inside an Complex element is stored as a column value. In that case will this redesign work. Or is there any other way to approach re-desgin the XML Schema.

Thanks. I think that leaves out my option to create a totally new Schema to suit my XML files.
Only other option we have is to use Annotations.
I think my colleague - eoin62 would have shared the XML Schema files earlier through your oracle email address.
Please refer thread - How to register multiple XSD files
But we received a reply and we knew very little on how to make changes to Admin.xsd and how would that solve our problem. Please correct me if i am incorrect. Because the biggest Schema was estimate.xsd that has close to 800+ elements. I am not sure if my colleague sent you the necessary tag names we use within the Schema. We have close to around 300 tags we use. But our combined XML Schema has close to 1600+ If we have to annotate, i thought it would be better we tell Oracle which tagswe need, which inturn should should help better create XMLtype table against a Schema and work on performance.
Your earlier reply was,
Basically in XML Schema Admin.xsd element AdminCompin WorkfileTypeneeds to be stored Out of line..
Add the annotations xdb:SQLInline=”false” and xdb:defaultTable=”ADMIN_COMP_XML”. to the element..
if you can share with our XML Schema on how to annotate or if you can share a location that shows how an annotated or non-annotated Schema works that would help us correcting our Schema files.
Thanks for all your support. We have gone a long way in XML Parsing in the last 6 weeks.
Edited by: beta32c on Feb 19, 2013 12:09 AM

Data Insertion, XML Schema Specifying Element minOccurs="1

An XML schema having an element with attribute minOccurs="1" has been successfully registered. A table was created based on that schema. Inserting data both with and without that element works successfully. Why is this?

The only thing right now, I can think of, is that the database doesn't recognize it as being controlled via / depends on a registered XML Schema. See the FAQ on this forum for examples (See here: How does XML DB handle XML Schema Validation ?

XML schema size restrictions

I was wondering what size restrictions there are on XML schemas? I'm developing a schema that has just raised the following error on registration.
ERROR at line 1:
ORA-31084: error while creating table "CAS"."swift564357_TAB" for element "swift564"
ORA-01792: maximum number of columns in a table or view is 1000
ORA-02310: exceeded maximum number of allowable columns in table
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 151
ORA-06512: at line 828
On removing a few elements from the schema it registers fine, but querying the generated table swift564xxx_TAB there is only ever one column, typed with an ADT that itself only has 5 elements. In fact there doesn't seem to be, on the face of it, any type that has more than 20-30 elements. Where does this error come from then?
Unfortunately the schema exceeds the 20k limit on postings. I can split it up and post it in two parts if this would help.
Thanks
Marc

Each attribute in the ADT and each attribute of attributes which are an ADT count as one column
Here's a snippet from the next version of the doc that may help...
3-20 Oracle XML DB Developer’s Guide, Rel. 1(10.1) Beta 2 Draft
A number of issues can arise when working with large, complex XML Schemas.
Sometimes the error "ORA-01792: maximum number of columns in a table or view
is 1000" will be ecountered when registering an XML Schema or creating a table
based on a global element defined by an XML Schema. This error occurs when an
attempt is made to create an XMLType table or column based on a global element
and the global element is defined as a complexType that contains a very large
number of element and attribute definitions.
The errors only occurs when creating an XMLType table or column that uses object
relational storage. When object relational storage is selected the XMLType is
persisted as a SQL Type. When a table or column is based on a SQL Type, each
Registering an XML Schema with Oracle XML DB
attribute defined by the Type counts as a column in the underlying table. If the SQL
Type contains attributes that are based on other SQL Types, the attributes defined
by those Types also count as columns in the underlying table. If the total number of
attributes in all the SQL types exceeds the Oracle limits of 1000 columns in a table
the storage table cannot be created.
This means that as the total number of elements and attributes defined by a
complexType approaches 1000, it is no longer possible to create a single Table that
can manage the SQL Objects generated when an instance of the Type is stored in the
database.
In order to resolve this problem it is necessary to reduce the total number of
attributes in the SQL Types that are used create the storage tables. Looking at the
schema there are two approaches that can be used to achieve this:
The first approach uses a ’top-down’ technique that uses multiple XMLType
tables to manage the XML documents. This technique reduces the number of
SQL attributes in the SQL Type heirarchy for a given storage table. As long as
none of the tables need manage more than 1000 attributes the problem is
resolved.
The second approach uses a ’bottom-up’ technique that reduces the number of
SQL attributes in the SQL Type herirarchy collapsing some of elements and
attributes defined by the XMLSchema so that they are stored as a single CLOB.
Both techniques rely on annotating the XML Schema to define how a particular
complexType will stored in the database.
In the case of the top down techniqueby the annotations SQLInline="false" and
defaultTable are used to force some sub-elements within the XML Document to
be stored as rows in a seperate XMLType table. Oracle XML DB maitains the
relationship between the two tables using a REF of XMLType Good candidates
for this approach are XML Schemas that define a choice where each element
within the choice is defined as a complexType, or where the XML Schema
defines an element based on a complexType that contains a very large number
of element and attribute definitions.
The bottom up technique involves reducing the total number of attributes in the
SQL object types by choosing to store some of the lower level complexTypes as
CLOBs, rather than objects. This is acieved by annotating the complexType or
the usage of the complexType with SQLType="CLOB".
Which technique is best depends on the application, and the kind of queries and
updates that need to be performed against the data.

XML Schema Component Naming Convention

Is there a naming convention when you create an XML Schema? For example,
When you create a Type component, then the first letter of its name should be upper case ie. BMW, Honda, AutombileEngine ...etc.
When you create an Element component, then the first letter of its name is lowercase ie. engine, car, guestCar ..etc.
Do we have such naming convention for XML Schema?
Thanks

I am giving this from my document which i prepared for one of my customer
2 General Guidelines for design of XML schema documents
The representation of data in an XML format will be a key component of development within SOA. Therefore, the design and development of XML schemas should be as rigorous an activity as designing and developing code or designing database schemas. As such, when creating an XML schema you should be working within a development process and working to a set of design guidelines and coding standards (when writing the XML schema file). XML schemas should be reviewed for accuracy and compliance with guidelines and standards. Each of the requirements in the list below is a general requirement for all XML schemas to be deployed in the SOA environment.
• Understandable: XML schemas should be clear, consistent and unambiguous. They should contain human readable documentation and, where appropriate, links to requirements or design documents.
• Semantically Complete: An XML schema should define, for one or more target XML documents, each and every element and attribute that is understood by your solution when processing target documents.
• Constraining: XML schemas are used as contracts between both publisher and consumer. As such, they must be able to be validated as concisely as possible. When designing an XML schema constraints should be identified for the values for all the elements and attributes that the application uses and relies on to the set of values that the application can handle. A valid document should imply valid data within the limits of what can be specified by the XML Schema language.
• Uniquely identifiable: XML schemas should import and include other XML schema files rather than duplicating types and elements locally.
• Reusable: XML schemas should be specified in such a way that types and other XML schemas can leverage elements. Every type defined in an XML schema that is the content type of an attribute or an element should be defined globally (i.e., at the top level in the Schema). Types that are defined globally can be reused in other XML schemas. Schemas should be separated into logical sections which can be included into the main schema file.
• Extensible: Schemas should be designed to be extensible—that is, new elements and attributes can be inserted throughout the document.
Every schema should use at least two namespaces – the targetNamespace and the XML Schema (http://www.w3.org/2001/XMLSchema) namespace.
Create typed elements that can be referred to by object elements:
Example:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.soa.com"
xmlns="http://www.soai.com"
elementFormDefault="qualified">
<xsd:complexType name="PersonType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="SSN" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.company.org"
xmlns="http://www.company.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="Person.xsd"/>
<xsd:include schemaLocation="Product.xsd"/>
<xsd:element name="Company">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
<xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
• Recognize that with XML Schemas you will not be able to express all your business rules.
o Express those business rules using XSLT.
• Use type definitions
Elements vs Attributes
• Use attributes for metadata about the parent element.
• Use attributes for data that is semantically tied to the enclosing element.
• Use elements for data that have a meaning separate from the enclosing element.
• Use attributes when the value will be frequently present in order to improve the human readable form of an XML instance document or reduce its size.
• If you don't know which to use, then use the element form (which is more extensible).
2.1.1 Element, Types and attribute names
Create a descriptive name without it being excessively long (no more than 32 characters).
Elements and Types should be named in Upper Camel Case. Upper Camel Case capitalizes the first character of each word and compounds the name (remove all whitespace).
Attributes should be named in Lower Camel Case. Lower Camel Case capitalizes the first character of each word except the first word and compounds the name.
Simple and Complex type names
XML Schema has separate symbol space for elements and types so they may have the same name. The best practice is to append the word "Type" to all simple and complex type names to aid in human readability and comprehension.
Element, attribute and type names MUST be in a singular form unless the concept itself is plural.
2.1.1.1 XML Schema versioning
Use major and minor version tracking:
Major—completely different structure and semantics, most likely not backward compatible
Minor—backward compatible changes which introduce new features without removing or changing the semantics of existing structures
2.1.1.2 Indication of version in the namespace URI
Specify a namespace URI as follows
http://$domain/$groupSpecifier/$namespaceTitle/$version
The groupSpecifier can include several levels, e.g., /www.soa.com/SOA/USA/.
An example namespace could be:
http://www.soa.com/SOA/order/2

Missing Imports System.Xml.Schema in MDKSAPProxy.vb

I have recently switched computers and I "believe" I have setup my SAP.NET connector 2.0 properly, but, when I generate my proxy the proxy file is missing the line Imports System.Xml.Schema as well as Form:= XmlSchemaForm.Unqualified from almost all XML declarations.
This creates problems with BPAIs not being able to execute. My old system is fine, and I did a compare and so far I'm not able to find why this is the case. Any help will be much appreciated.

Hi Tomasz,
how are you doing ?
the dependacies that most likely are the cause of your affliction are :-
1> librfc32.dll (this is in (\windows\system32) can be updated by SAPGUI, so the versioning if you use a previous release of SAPGUI could give unpredictable results while generating proxies
2> JRE / J2SDK, please check the version you are running
a stable one i use is 1.4.2_12
do you receive a error message ?
i would recommend time to be spent re-installing the Connector, which should be simpler than debugging and fixing the installation
let me know if you need a stable version dependancy list and order of installation from my side
also tell me as much as you know about your current environment , products installed that could affect :
1> JRE / J2SDK
2> NCo
3> SAP GUI
with respect,
amit

How to create our own XML Schema (.xsd) in Weblogic WorkShop

Hi,
I am new to Weblogic Workshop.I want to create one xml schema with custom elements.
when I am creating a file xml schema(.xsd).The file contains default namespace and no child elements in it.I don't know how to add elements to that file.
please tell me how to add parent elements and child elements and also our own xml namingspace.

Hi Sivaram,
Unfortunately, the 8.1 IDE did not have special tooling for schema generation.
You will need to create it by hand or using an external tool
If you are using an external tool to create the file within the schema project, you might want to disable the schema project auto build, which will be triggered every time a file save takes place
cheers
Raj

Web Services.........XML schema of operation parameter?

This is a generic question :)
If my implementation fucntion is accepting a XML how can we embed the schema of the input XML in the WSDL so that it can be discovered by user/client?
Is it possible to define the input XML schema in the element binding? and how?
In contrast if the implementation function is accepting primitive types as input data , the how does the user/client encode(XML marshall) the information in his post or soap message so as to be understood by the web service.
Or
the user can directly write a client program and pass primitive parameters,marshall unmarshalling is done automatically?
No need to worry about how the data is carried in the post and soap messages?
Also what are the differrent ways in which a web service can be used and consumed?
If the user doesnot want to write a client program, but directly pass an http post or soap message, how will the user know how to write the POST/SOAP message in appropirate format(with the rigth XML format in the post body/soap message)!

Hello,
There's not one. The primary vision for the web-services.xml file
was/is to be a linkage between wsdl/soap and the j2ee environment. It
was not intended to be a starting point for building an application, but
a semi-private intermediary.
HTHs,
Bruce
Toni Nykanen wrote:
>
Hi there!
I'm just curious to know whether there exists any dtd or schema
for wls 7.x web-services.xml file?
The diagram in
http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
shows one order for the contents of the web-service element,
whereas the examples reflect another (being types,
type-mapping, components, operations).
Why are the example web-services.xml not tagged with the
information of the location of the schema?
Of course building web-services.xml manually is not the first
thing to try, but since the contents are documented and since
it gives the best control over the process, it makes sense.

XML Schema binding - dynamic form

I am new to Designer and XML. I have been given a basic interactive form and have persevered for a couple of (often frustrating) weeks to extend its functionality to link to an xml schema and provide for dynamic record creation. Unfortunately I am still having problems when adding new instances of subforms. I have a main form for reporting issues. Underneath it there are major components on a subform (can be multiple major components for each issue) and under major components are sub-components (can be multiple sub-components for each major component) on a child subform of major. I can add and delete instances of the subforms for both levels of records. I have created an xml schema based on the form since it already existed, and so the form fields have not inherited properties from the schema. However, I have bound the fields in the form to the xml fields through a data connection. The schema basically looks as follows (bot not literally the same as you will see from the tags): <element complextype issue> <element issueId string/> ... ... <element complextype majorcomponent unbounded> <element majcomponentname string/> ... <element complextype subcomponent unbounded> <element subcomponent string/> <element quantity string/> ... ... </element> </element> </element> My problem is as follows: When I add an instance of a sub-component or major component subform, the first new instance appears to work correctly. However, every subsequent one inherits the values of the previous record and when it is changed, it changes the values of existing fields of the same name but of a different node. When I change each element in the xml schema to "unbounded", the forms appear to work properly but the values are then not nested correctly in the outputted xml data file (many records will appear under one sub-component, for example, when a new sub-component should be added for each). I suspected my problem might be that the "unbounded" property in the schema of the major component and sub-component elements are not linked to the Designer form because the major component and sub-component subforms are not bound to the xml schema. The reason they are not bound is because if I bind the subform, the first element, major/sub component name as applicable, loses its binding. I am sorry if this doesn't make any sense but I am hoping that someone might recognise the problem I am talking about as it is really creating much bother. Thanks.

Thanks Justin for the reply. Unfortunately I can't explain exactly what was happening because I didn't keep sufficient notes and now the form is behaving differently. You are right in that when I bind the subform to the xml schema element, child fields do change their bindings from a full to a relative path. I had seen this before on all except the first field on a subform, which had losts any binding reference at all.
I finally gave up on the schema and bound the forms to sample xml data. This fixed my problem. Now (several days later), I have revisited the problem and deleted my data connection to the xml file to connect to the schema once again. I am quite sure I have not changed the schema at all, nor the form, but for some reason it now appears to work correctly.
I will continue to work with it, once again but thanks very much for your interest.

XML data within dynamic form

Hi,
I'm trying to make a new XML Schema connection inside the form designer, I successfully made the connection and get the data inside my form, but I have only one problem, I have a huge number of records which I decided to make them as a dropdown list, they are about 11000 records, OK, now to the problem which is if I save the form as a static pdf form the list will be filled completely with the data came from the XSD file, and the produced file size is about 3 M, but if I save it as dynamic pdf form, the produced file size is about 400 K, but if I tried to access the dropdown list inside the file, it takes forever to load, without getting any result at the end.
OK, my personal conclusion is that in case of the static forms the data saved inside the pdf file, but in case of the dynamic forms the data is not saved there.
I need to save the file as dynmic pdf because I have a table that needs to add new row accoriding to the user click on a button of (add new row).
So, can any one help me to fix this issue?

Sorry, I found the solution:
when I use the Adobe Reader 8.0.0 or Adobe Acrobat professional 8.0.0
the stuff works normally, but in case of Adobe Reader 8.1.1 or Adobe Acrobat professional 8.1.1 this problem happens,
Now I'll explain:
1- I have a form with dropdown list.
2- I want to populate this dropdown list from XSD file has structure similar to the following:
=====================================================================
<?xml version="1.0" encoding="ISO-8859-1" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="shipRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="orders">
<xs:complexType>
<xs:sequence>
<xs:element name="order" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="shipVia">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Ground"/>
<xs:enumeration value="2 Day Air"/>
<xs:enumeration value="Overnight"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
====================================================================
but with one main difference, that the element of shipVia has about 11000 of (<xs:enumeration ) elements.
3- when I made the normal steps of make new connection to XSD file, it walked with me normally without any errors.
4- incase I save this form as static pdf file, then open it with adobe professional, the menu is working smoothly and load the data inside perfectly.
5- incase I sace this form as dynamic pdf file, if I try to open the dropdown list, it takes forever to load the data.
very starnge that this problem happen with the newer version, so any idea for this??

What am I doing wrong with my form - XML schema producing inconsistent results

I have an interactive dynamic form built in LCD 8.2. The idea is that users fill in the form to indicate any fields that they want to update on our directory.
We do not have the necessary plumbing to get it to feed directly to the directory so the workaround is that the form generates an XML file. These files are then imported into Excel and then that file is submitted as a bulk update request.
I have a schema that I have embedded in the form using the Data Connection
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MySite">
<xsd:complexType>
 <xsd:sequence>
 <xsd:element minOccurs="0" maxOccurs="unbounded" name="general">
 <xsd:complexType>
 <xsd:all>
 <xsd:element minOccurs="0" maxOccurs="1" name="FullName" />
 <xsd:element minOccurs="0" maxOccurs="1" name="StaffNumber" />
 <xsd:element minOccurs="0" maxOccurs="1" name="JobTitle" />
 <xsd:element minOccurs="0" maxOccurs="1" name="Responsibilities" />
 <xsd:element minOccurs="0" maxOccurs="1" name="LineManager" />
 <xsd:element minOccurs="0" maxOccurs="1" name="LMStaffNumber" />
 <xsd:element minOccurs="0" maxOccurs="1" name="AltContact" />
 <xsd:element minOccurs="0" maxOccurs="1" name="AltSE" />
 <xsd:element minOccurs="0" maxOccurs="1" name="Unit" />
 <xsd:element minOccurs="0" maxOccurs="1" name="TelExt" />
 <xsd:element minOccurs="0" maxOccurs="1" name="WorkMobile" />
 <xsd:element minOccurs="0" maxOccurs="1" name="OutHoursTel" />
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
I use this same schema in Excel and then generate a test file from my form and then import it. All goes well.
I then try it again or get someone else to try it and it fails. What am I doing wrong? I thought that embedding the schema into the form would mean that it would become part of the form but I keep getting an error message saying it cannot find an XML map that corresponds to the data.

Thanks for your reply.
The form is fine and no error messages are evident until I attempt to import an xml file into Excel. The schema is very, very basic and no validation has been applied.
I've looked at the form today to investigate what the problem may be and have discovered three issues.
I tried with two different versions of the form to try and work out why one version worked and the other did not. The only obvious difference between them was that one had been Reader Enabled and it was this form that did not work.
The non-enabled form produced this output:
<?xml version="1.0" encoding="UTF-8" ?>
- <MySite>
- <general>
<FullName>th</FullName>
</general>
</MySite>
The enabled form produced something different.
<?xml version="1.0" encoding="UTF-8" ?>
- <xfa:data xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/">
- <MySite>
- <general>
<FullName>gt</FullName>
</general>
</MySite>
<MySite />
</xfa:data>
Files with this extra line of code would fail to be imported into the Excel file.
Another issue was that the Reader Enabled form had a completely different file path for the embedded schema. In the non-enabled version the path pointed to the correct location on my personal drive. The Reader Enabled version could not find the schema as the path was incorrect and was pointing to a folder on the temporary drive. At no point had I manually amended this path to point to there!
The non-enabled form allowed me to import an xml file whereas the enabled form gave me an error message stating that:
"The document restricts some Acrobat features to allow for extended features in Adobe Reader. To create a copy of the document that is not restricted (and has no extended features in Adobe Reader), click Save a Copy."
Are these expected behaviours or is there something wrong?

Use SubForm Set for a choice in XML Schema

I have questions on subformset, the parameter to the 'setInstances' method and the use of 'intial' attribute of 'occur' element of XFA. 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. I use setInstances(1) and setInstance(0), but I could not find any documentation on the description of the parameter of setInstances. Anyone can take a look at it and help? Thanks. Hongwei Li 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. ========================================================================== <event activity="change"> <script contentType="application/x-javascript">if(this.rawValue==true){ _customerNumber.setInstances(1); _correspondenceAddress.setInstances(0); } else{ _customerNumber.setInstances(0); _correspondenceAddress.setInstances(1); }</script> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" id="XFASchemaXSD3"> <xsd:element name="us-correspondence-address"> <xsd:complexType> <xsd:choice> <xsd:sequence> <xsd:element ref="name-1"/> <xsd:element ref="name-2" minOccurs="0"/> <xsd:element ref="us-postal-address"/> </xsd:sequence> <xsd:element ref="customer-number"/> </xsd:choice> </xsd:complexType> </xsd:element> <xsd:element name="name-1" type="xsd:string"/> <xsd:element name="name-2" type="xsd:string"/> <xsd:element name="us-postal-address"> <xsd:complexType> <xsd:sequence> <xsd:element ref="address-1"/> <xsd:element ref="address-2" minOccurs="0"/> <xsd:element ref="city"/> <xsd:element ref="state" minOccurs="0"/> <xsd:element ref="postcode" minOccurs="0"/> <xsd:element ref="country"/> <xsd:element ref="email" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="phone" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="fax" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="customer-number" type="xsd:string"/> <xsd:element name="address-1" type="xsd:string"/> <xsd:element name="address-2" type="xsd:string"/> <xsd:element name="city" type="xsd:string"/> <xsd:element name="state" type="xsd:string"/> <xsd:element name="postcode" type="xsd:string"/> <xsd:element name="country" type="xsd:string"/> <xsd:element name="email" type="xsd:string"/> <xsd:element name="phone" type="xsd:string"/> <xsd:element name="fax" type="xsd:string"/> </xsd:schema>

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

Forms pulling Multiple Records from an XML Schema and XML data files - Adobe LiveCycle Designer

I built a form in Adobe LiveCycle with an xml schema and data file. The problem is with how the form renders the xml data file.
I have a statement element that consists of about 6 fields (statementID, statementName, statementAddress, statementCountry, statementZip, statementDate, etc) of data in the schema that allows for multiple iterations - so one xml data file can contain multiple statements. These fields allow for null values.
But here's the problem: When any of the statements - say statement 2 of 6 - has a null value in one of the fields, if the xml data file doesn't have a placeholder
(example of placeholder: <statementName type="String"/> )in the xml for that field, my form pulls the field value from the NEXT statement.
This corrupts all the rest of the statement records, as this field is shifted up for all the rest.
I know that in the past I haven't needed a placeholder when a field was null. But I'm wondering if when the data allows for multiple records the xml data file needs to generate the placeholder. And where is the problem? In the Schema? The xml data file? My form? And the 64-thousand-dollar question: How to fix it?

If your <statement> element is the one that repeats, it should be bound to a subform with the binding string of something like $.statement[*]. Then in that subform should be your fields and they should have bindings of $.statementID, $.statementName, $.statementAddress, etc.
Kyle

How to handle tables data in XML schema based adobe form

Hi all,
I am working on the CRM business partner creation by using Interactive adobe form with following steps:
1) Uploaded the offline Interactive adobe form to online interactive adobe form via WebDynpro ABAP;
2) Capture XML data into corresponding BAPI structures;
3) Save all the changes to database via BAPI.
The adobe form contains customer information as well as several table views which are bind with the context created in WebDynpro: Node NEW_BP_NODE cardinality 1:1 with single attributes and table type attributes (1:n): COLOUR_COMP, MEN_COMP etc.
While converting the xml format data to SAP context format, It is fine to use following routine to find the single attribute and map to the BAPI structure to do the database update.
NODE = DOCUMENT->FIND_FROM_NAME( NAME = 'XYZu2019).
XYZ = NODE->GET_VALUE( ).
Question: how to convert the xml table data to SAP context format in WebDynpro ABAP?
The XML table data looks like below.
<?xml version="1.0" encoding="UTF-8" ?>
<NEW_BP_NODE>
<COLOUR_COMP>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX>000</ZZTFLDRZ2AQX>
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX>000</ZZTFLDTC2DQX>
<ZZTFLDOR2UQX />
</DATA>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX />
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX />
<ZZTFLDOR2UQX />
</DATA>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX />
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX />
<ZZTFLDOR2UQX />
</DATA>
</COLOUR_COMP>
<MEN_COMP>
<DATA>
<ZZTFLD4V2V7V />
<ZZTFLDYD2N7W>000</ZZTFLDYD2N7W>
<ZZTFLDX32I7W />
<ZZTFLD2D2W7W />
<ZZTFLDGD2A7W />
</DATA>
<DATA>
<ZZTFLD4V2V7V />
<ZZTFLDYD2N7W>000</ZZTFLDYD2N7W>
<ZZTFLDX32I7W />
<ZZTFLD2D2W7W />
<ZZTFLDGD2A7W />
</DATA>
</MEN_COMP>
Thanks in advance for your help.
Michelle

Hi,
Just follow these steps:
1. Create interactive form UI element in your view.
2. Now provide Datasource and PDFSOURCE to it in form properties.
3. Now give a template name prefix with 'Z' or 'Y'.
4. Double click on it. It will prompt for interface name.
5. Provide interface name prefixed with 'Z' or 'Y'.
6. Click on Context button in the Pop up window and provide the node you have selected as DATASOURCE.
7. Click ok and it will open the form designer.
8. In this way you can create a XML Schema based Form.
9. Activate the interface and design the form providing layout type and other details.
Hope it will help.
Regards,
Vaibhav

Xml Schema xs:choice element in dynamic forms

Similar Messages

Maybe you are looking for