B2B Integration 10.4 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Document Types | Creating an IS Document Type | Derived Types and IS Document Types | *doctype Fields in Document Fields
 
*doctype Fields in Document Fields
When converting XML to a document (IData object), a complex type in the XML is represented in the IData object as a Document field. During the conversion while parsing the XML, Integration Server checks complex types for the xsi:type attribute. An xsi:type attribute specifies that the type in the instance document overrides the type definition that was defined in the schema. When Integration Server converts a complex type that corresponds to a derived type, it adds the *doctype field to the Document field in the IData object. Integration Server sets the *doctype field to indicate that the Document field is an instance of a derived type instead of the base type. Specifically, Integration Server sets the *doctype field to the fully-qualified name of the IS document type that corresponds to the value of the schema type name specified in the <xsi:type> attribute.
For example, a complex type in XML being converted might include the following:
<invoiceAddress xsi:type="order:USAddress"
When Integration Server generates the Document field for the invoice address, it will add a *doctype field and set its value to the fully-qualified name of the derived document type that corresponds to the schema type name “order:USAddress” (for example, orders:docType_Ref_order_USAddress).
When working with a Document field that was converted from XML, do not delete or edit the *doctype field.
Note: When converting XML to a document (IData object), if Integration Server encounters an <xsi:type> attribute in a simple type, Integration Server ignores it. No *doctype field is added.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release