Master data objects
The integration framework provides a selection of predefined integration content for
master data, which generally consists of accounting, people, storeroom, labor, classification, and
vendor data.
Asset object
The MXASSET object structure allows for bidirectional synchronization of asset information, including attributes that define meters.
Chart of Account object
The MXCOA object structure allows for bidirectional synchronization of chart of accounts data.
Classification item object
The MXCLASSIFICATION object structure allows for bidirectional synchronization of classifications, including Class Use With, Class Specs, and Class Spec Use With.
Craft object
The MXCRAFT object structure allows for bidirectional synchronization of craft information. Craft information includes crafts, craft skills and craft rates.
Financial project object
The MXPROJ object structure allows for bidirectional synchronization of financial project information. This object structure synchronizes individual tasks and projects as separate messages. It does not synchronize a project and all its child tasks in a single message.
General ledger (GL) component object
The MXGLCOMP object structure allows for inbound synchronization of GL components.
Labor object
The MXLABOR object structure allows for bidirectional synchronization of labor information, including person and labor craft rates.
Person object
The MXPERSON object structure allows for bidirectional synchronization of person information, including phone, email, and SMS data.
Person/user object
The MXPERUSER object structure allows for bidirectional synchronization of person/user information. This object structure supports status changes.
Storeroom location object
The MXSTORELOC object structure allows for bidirectional synchronization of storeroom, labor, and courier locations.
Vendor (Companies) master object Structure object
The MXVENDORMSTR object structure allows for bidirectional synchronization of vendor master data.
Vendor (Companies) object
The MXVENDOR object structure allows bidirectional synchronization of organization-level vendor data, including contacts.