Creating multiple Records in a RecordList

, ,
1

I have what must (hopefully) be a newbie issue. I’ve created a Record from an XML Schema that contains this element:

<xs:element name=“Parameters”>
xs:complexType
xs:sequence
<xs:element ref=“Parameter” maxOccurs=“unbounded”/>
</xs:sequence>
</xs:complexType>
</xs:element>

<xs:element name=“Parameter”>
xs:complexType
xs:sequence
<xs:element ref=“Value” maxOccurs=“unbounded”/>
</xs:sequence>
<xs:attribute name=“Position” type=“xs:positiveInteger” use=“optional”/>
<xs:attribute name=“Name” type=“xs:string” use=“optional”/>
<xs:attribute name=“DataType” type=“xs:string” use=“optional”/>
</xs:complexType>
</xs:element>

… etc.

Now my first problem is that “Parameters” gets automatically created as a Record instead of a RecordList. This seems wrong since the schema defines it as having a child with maxOccurs=“unbounded”.

Anyway, I changed it to be a RecordList. Now the bigger problem, is that when I submit an XML doc containing multiple “Parameter” elements via TN and convert it into a Record using bizdocToRecord, I only get the last “Parameter” element as a record in my boundNode. Specifically, I submit a doc with 13 "Parameter"s and I only get one record (Parameter[0], containing the last parameter) in my resulting RecordList.

I’ve also specified the Record to use for this process in the options tab of my Doctype in TN. Anyone know what I’m doing wrong? TIA.

Mike R.

2

I’ve discovered a bit more about this problem. Firstly, I’ve finally gotten my head around this whole Record/RecordList thing and it doesn’t seem to have been the issue.

What may have been a problem is the way I created the original Record. My first step was to import my XSDL schema as a wM schema. This was easy enough. I then created a new Record based on that wM schema. In this scenario, the bizdocToRecord didn’t work (as described earlier.

I deleted these records and schemas and started fresh. This time I began by creating a new Record based on the XSDL schema from my filesystem, and allowed IS to automatically create the wM schemas it needed. In this scenario bizdocToRecord worked as expected.

However, I also changed my input slightly for this second attempt. A default namespace declaration was causing some difficulties, so I used explicitly prefixed elements in the second submission. Lastly, my colleague is still experiencing the bizdocToRecord problem after making both changes. So I’m not completely sure yet what was/is causing this behavior.

Any further ideas would still be appreciated.