XML Schema Line
XML Schema Lines
The XML Schema Lines section provides a comprehensive overview of the XML schema structure and its associated attributes. It allows you to define and configure various elements within the XML schema for effective data processing and validation.
- XML Schema Code indicates the XML schema code. e.g. OPENTRANS, xRechnung.
- Document Type indicates the document type. e.g. INVOICE.
- Sorting No indicates the sorting number.
- Entry No. indicates the entry number.
- Parent Entry No. indicates the parent entry number.
- Name indicates the name.
- Value indicates the value.
- Fixed Value to select whether the value will be fixed or not.
- Is Mandatory to select whether the schema is mandatory or not.
- Ignore if no Child Element has Value to select whether ignore or not if child element has no value.
By utilizing the XML Schema Lines functionality, you can precisely define the structure and characteristics of your XML schema, ensuring accurate data representation and adherence to specified standards. This enables smooth integration and seamless data exchange within your system or with external entities following the defined XML schema guidelines.
Additional Fields and Formatting
- Type, Data Type, and Namespace describe the XML node and how its value is emitted.
- Format String supports special handling; use the value
texton blob sources to output readable strings instead of Base64. - Source Table No. / Source Field No. highlight exactly where the value is pulled from.
- Example Value helps document the expected payload for downstream consumers.
Working with Blob-Based Notes
- Header notes are now stored in field 13 Invoice Notes Blob on table 5563231 mseBC mseDoc365 S. Inv.Buffer. Point schema lines to this field for IncludedNote or Note elements.
- Line descriptions and notes rely on the blob fields mseBc mseDoc365 Ln. Desc (5563222) and mseBC mseDoc365 Ln. Note (5563223) on the sales invoice and credit memo line buffers.
- Combine Data Type = TypeBlob with Format String = text to stream the memo content as plain XML while still filling the legacy text fields for compatibility.