Why would an integration be repeatedly setting and unsetting a customer address?

AI generated answer (using internal Slack threads):

An integration could be repeatedly setting and unsetting a customer address due to several reasons: 1. Calculated Field: The 'shipaddress' field could be a calculated field, created from the address elements in the addressbook entry marked as default shipping. Any update to the sublist seems to force it to be recalculated, causing the field to be set and unset multiple times. 2. Order of Setting Fields: In dynamic mode, the order in which fields are set matters. If other fields that impact the address (like subsidiary, customer, department, class, location, account) are set after the address, it could cause the address to be reset. 3. Workflow or User Event Scripts: There could be workflows or user event scripts that are making edits in a create context only, causing the address to be reset. 4. Contact Role: If a customer has a contact with a role of "Primary Contact" with a different address, NetSuite could be copying this to the Billing Address on all transactions, causing the address to be reset. 5. System Behaviour: It could also be a default system behaviour where the 'shipaddress' field is triggered multiple times when a customer is chosen. This could cause the address to be set and unset multiple times. To mitigate this, you could try setting the address multiple times, or ensure that the address is set after all other fields that could impact it. You could also check for any workflows or user event scripts that could be causing this behaviour and adjust them accordingly. If a contact with a "Primary Contact" role is causing the issue, you could remove this role from the contact. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******