Editing and saving a single-occurrence Customer Order address fails with a generic 'Exception while sending data' / 'Database error occurred' error, with a SOAP fault buried in the debug log referencing an unclosed XML element in an address-validation call.

All FAQ questions / Distribution, CRM, and commerce

Answer

Check the address name and address lines for an ampersand (&) character — an unescaped '&' in the address data being passed through to an address-validation/tax-service integration (like Avalara) breaks the underlying XML/SOAP payload, producing exactly this kind of 'unexpected end of file, elements not closed' fault. Removing or replacing the '&' character in the address resolves it.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Distribution, CRM, and commerce questions