When creating records, default values are automatically populated. You only need to fill in the fields you want to change, leaving all others at their default values. However, some fields depend on other fields (e.g., the document type or VAT country determines the VAT rates). For this reason, the application builds a dependency tree of related fields and applies values in an order that ensures any field influencing another is set first, followed by the dependent field. Reversing this order would cause the dependent value to be overwritten.
Thanks to this behavior, the order in which attributes appear in the XML file does not matter. The order of individual records does matter, however (e.g., creating a company in the address book before entering related orders).
The cascading effect of field dependencies may also result in a value being changed even if it was not explicitly modified during an incremental update.
When a record is saved, validation is performed, and the caller is notified of any errors, warnings, or informational messages that may arise.