Field mapping
In Arabic ربط الحقول
Field mapping is the set of rules that pairs each field in one system with the matching field in another, and translates values such as codes between them.
In plain words
Two systems almost never name things the same way. One calls it customer code, the other account number; one writes payment terms as NET30, the other as 30D. Without a map, every integration or import needs custom code, and every change on either side breaks it.
A field map has two parts. The first pairs fields: this one goes to that one. The second is a lookup table that translates values, so a payment term, tax code or unit in one system becomes the right code in the other. Both are kept as settings, so they change without a developer.
The common mistake is mapping values that are not in the table yet. A new payment term is added on one side, the lookup has no match, and the record is either rejected or sent with a wrong default. Update the lookup table whenever a list changes.
- Customer code, sent as account_no
- C-1042
- Payment term Net 30, sent as terms
- NET30
- Currency, sent as curr
- SAR
- Unmapped fields
- 0
In Axon Suite
How Axon Suite handles it
In Axon Suite you pair each Axon Suite field with the other system’s name, and translate values such as payment terms or tax codes through a lookup table.
Feature
Signed webhooks you can replay
Axon Suite posts each new customer to your own middleware through your field map, signed so you know it came from you. Failures are retried, kept for replay, and a kill switch stops sending while you fix the other end.
Open: Signed webhooks you can replay