Defining tables and fields

The XML Autoload Utility field and table definitions, provided here, are used for adding new objects or changing or deleting objects in the Partner Manager database.

The following are field descriptions for the XML tables

• Field Label is the label on the screen as it appears in Partner Manager.
• FieldName/Tag is the database field name (if one exists), and is used as the XML tag.

  There are two distinct sets of XML tags included in the XML Autoload Utility: one set is used to add data and another set is used to change existing data. These separated tags ensure backward compatibility for users of prior versions of this utility. (Your script generation routines for adding data remain unchanged.) The separation of tags also prevents you from accidentally changing data when you intended to add data. The new change and delete tags always end with Change or Delete, for example, AddChangeDelete. The tags related to Documents on a Trade Link always end with AddChangeDelete, for example, X12InboundGroupsAddChangeDelete.

• Req'd means this field must be in the input to AutoLoad, it is not the database definition of required. The abbreviation fk = Foreign Key (that value must exist in the specified table).
• Max. Len. is the maximum length of the field (minimums, if any, are in the notes).
• Validation defines the valid values for the fields.
• Notes contain detailed information about the tag.

  System generated fields such as Surrogate keys, Optimistic Locking Fields, and Audit Information (for example, CreatedBy/DateCreated) and are not listed here. These fields are populated automatically by the Autoload Utility. Leading and trailing spaces, if any, are trimmed before saving to the database. CreatedBy is set to AutoLoad so that any problems associated with this utility can be tracked.