Quote/Procurement: Address field values exceed character limits in downstream integrations

Description

We are seeing errors in downstream integrations caused by address field values that are too long for the receiving system to accept. Two flows are currently affected:

1. Pushing a delivery address to Dynamics Business Central, where the city field exceeds the system's 20-character limit.

2. Pushing a ship-to address to a distributor via the procurement/orders module, where the state field contains a bilingual value ("Flandre Occidentale / Oost-Vlaanderen") that exceeds Autotask's character limit for that field.

It is unclear whether these long values originate from the address auto-fill/postal code lookup feature, from Autotask contact data, or from manual input. The current workaround is to manually shorten the affected field before retrying.

Steps to reproduce

1. Have a quote or order with an address where the city or state field contains a value exceeding the downstream system's character limit.

2. Attempt to push the quote to Dynamics Business Central, or submit a procurement order.

3. Observe the error referencing the field length violation.

Expected behaviour

Salesbuildr should either validate address field lengths before attempting to push to downstream systems, or surface a clear warning when a value would exceed the limit of the target system.

Impact

Quotes cannot be pushed to Dynamics and procurement orders cannot be submitted until the field is manually corrected. If the quote is already approved, the customer cannot edit the address themselves, requiring manual intervention.

Open questions for investigation

• What is the maximum allowed length for each address field (city, state, street, zip) in each downstream system: Autotask, Dynamics, and distributor APIs?

• What is the source of the bilingual state value ("Flandre Occidentale / Oost-Vlaanderen")? Is it coming from the postal code lookup, from Autotask contact sync, or entered manually?

• Are other address fields (street, zip) at risk of the same issue?