Chapter 9: XML document integration (II)-XML structure

This article is only for communication between ax practitioners and fans. Please do not repost it because of copyright issues in the original article.
XML structure
The primary goal of ax's XML document function is to reduce the time used to implement new XML documents. Most systems integrated with ax need to map columns without paying attention to the architecture. Some of the words are translated into patterns, and some are translated into diagrams, in SQL server2005, the translation is the architecture. Here we follow this translation method. XML Schema describes the content structure of an XML file. If you understand this meaning, it will be OK. If you cannot, you can directly use schema, there is no need to waste too much time for this term, and there are a lot of things that can be easily said). The product team decided to implement the internal architecture (schema) in the form of APIs ). In this way, only one ing is required for each integration endpoint. Most ax developers are familiar with the internal schema.
Obviously, queries in AOT should be used for representation. The data source of AOT query is directly associated with the table. The fields contained in these tables are converted into attributes in XML. Since EDT is defined in AOT, XSD (XML schema definition) can be limited by the available metadata describing the data type, such as the field size.
In the document, attributes appear in a fixed order as XML Community This method is widely adopted. The query structure supports this method. Tables appear in the order of query. the XML document Framework Automatically sorts fields in alphabetical order, so that documents do not need to be developed manually. Note: If a table is referenced by multiple nodes in the query, the XML Schema must have a unique name. The field name of the table is used for XML reference, the table name uses the table name in the query.
The limit is that each query can only be composed of one root table. The unique entity key of the XML document can be associated with this root table. To support 1: n needs to use outer join. If the limit must be, you need to use inner join, outer Join and inner join are not used to limit the relationship between 1: N and, but to differentiate whether the primary table records are displayed when the subtable does not have the corresponding records of the primary table, outer Join shows that inner join is not displayed. This is not an EDGE connection between 1: N and. I cannot figure out the meaning here for the moment. Let's wait until I get it blank ).
Figure 9-3 shows the ing between referenced queries and XML structures in the axd <document> class in AOT.

Figure 9-3: Relationship between AOT query and XML document structure