This article is only for communication between ax practitioners and fans. Please do not repost it because of copyright issues in the original article.
An important feature of axd-like is to serialize and deserialize class instance objects for XML documents of ax. The architecture of these documents (Schemas) is generated through iterative query, the schema (Schemas) is defined, and the XML element is named using the name and attribute of the ax <Table> class.
Create a <Table> element for each table in the query. These <Table> elements contain all the attributes of the corresponding <axtable> class. These attributes are embodied in Parm <fieldname> Get/set method. The naming rules must be followed, because you cannot specify whether the field values can be serialized by assigning attributes to the X ++ class field names and methods. After an element shows its attributes, it is embedded in the <Table> element, which is the <child-Table> element used by some columns to present the child nodes defined in the query. If a <Table> element does not contain child nodes, it only containsThe element of the parm <fieldname> attribute.
Note: A query can contain only one root-level table. Multiple root-level tables may cause an error in the framework and terminate the execution.
To implement the 1-N relationship, you must set the joinmode attribute of the query to outerjoin ). If there is no special reason to use the relationship, maintain this setting ). In most documents in ax, this method is mandatory and only containsInventdimYou can use innerjoin to join a table.
