Summary

iPaaS.com customers can be transferred into Microsoft Dynamics NAV through the Customer From iPaaS.com mapping collections. The Add collection creates a new NAV customer and the Update collection refreshes an existing one; both write to the Microsoft Dynamics NAV Customers endpoint.

ID Format

Manual Sync ID Format. To sync a single customer on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Customer From iPaaS.com transfer, and enter the iPaaS.com customer's number. The integration writes this value as the Microsoft Dynamics NAV customer number (No.), which is the key used to match and update the record on later syncs.

Pattern: the iPaaS.com customer number
Example: C00123

External ID Format. After a successful sync, the Microsoft Dynamics NAV customer number (No.) is stored as the external ID that links the iPaaS.com customer to its NAV record.

Deleted Record Support

Outbound delete is not supported. The Customer model's Delete method is not implemented, delete mappings are not included in the default templates, and customer deletions in iPaaS.com do not propagate to Microsoft Dynamics NAV. Remove a customer in NAV directly if required.

Custom Field Support

This collection supports custom fields. To populate a Microsoft Dynamics NAV customer field that is not in the standard mapping list, add a subscription custom field whose name matches the NAV field name and map its value; the integration adds each such field name and value directly to the request it sends to NAV. The name must be a valid customer field in your NAV environment, or NAV rejects the request.

Mapping Collection Status

Status: Enabled

Trigger Events: Automatic transfers are activated by the subscriber in the iPaaS.com subscription configuration's Outbound Data Flows section, by enabling the iPaaS.com record Create and Update events that should dispatch this collection. No automatic transfer runs until they are enabled there. Manual Sync (see ID Format) is available at any time regardless.

Duplicate or Conflicting Mappings

Other collections that write to the same record. The Customer Add and Customer Update From iPaaS.com collections both target the same Microsoft Dynamics NAV customer record. The Company From iPaaS.com collections also write to the NAV Customers endpoint (NAV stores companies as customer records), so customer and company transfers share the same NAV table — keep iPaaS.com customer numbers and company Ids distinct so the two flows do not write to the same NAV record.

Collision handling. Configurable collision handling is not used for customers; it applies only to the Sales Order collections.

Duplicate Matching

A distinct mechanism from collision handling: before creating a customer, the integration links to an existing Microsoft Dynamics NAV customer to avoid creating a duplicate — matching first on the customer number, then on the email address — and stores the NAV customer number as the external ID. Two subscription settings refine this matching and must be configured together:

CommaSeparated Customer CustomField Matching Name & Value — optional. Enter a single customFieldName,customFieldValue pair (exactly one comma), for example Active,yes. When set, and an incoming customer has a custom field with that name and value, the integration prepends the CustomerNumber Duplicate Prefix to the customer number before searching NAV for an existing customer.
CustomerNumber Duplicate Prefix — required whenever the matching setting above is set. If the matching setting has a value but this prefix is empty, the transfer fails with: "CustomerNumber Duplicate Prefix preset is null/empty while CommaSeparated Customer CustomField Matching Name & Value preset has this value: \<value>".

Supported Child Collections

None. Customer address detail is mapped onto the customer record itself (see the Mappings section), not as a separate child collection.

System Caveats

Microsoft Dynamics NAV Caveats

The Customers OData web service must be published in Microsoft Dynamics NAV with the service name exactly Customers, or customer records cannot transfer.
Microsoft Dynamics NAV field requirements are governed by your company configuration and are not published in a public API specification. Review your NAV customer card for fields marked as required and confirm each is mapped before enabling the collection; an unmapped required field causes NAV to reject the record. A Customer Posting Group is commonly required to create a customer that will carry transactions.
Validate field requirements in a staging environment before relying on the transfer in production.

iPaaS.com Caveats

The address, city, county, post code, country, and phone fields populate only when the iPaaS.com customer has an address flagged as the primary billing address.
The customer Name is mapped from the iPaaS.com First Name only; adjust the mapping if a full or company name is required in NAV.

Setup Requirements

Microsoft Dynamics NAV Configuration

Publish the Customers OData web service (Departments → Administration → IT Administration → Services → Web Services), with the service name exactly Customers. See the Installation Instructions for the full endpoint setup.

Authentication

The integration authenticates to Microsoft Dynamics NAV using the connection credentials configured in the subscription settings (API Url, Domain, Username, Password, Environment, Company Name). See the Connections and Settings documentation.

Integration Flow

A customer is sent from iPaaS.com to Microsoft Dynamics NAV (Add for a new customer, Update for an existing one).
The integration checks for an existing NAV customer by customer number, then by email; if found, it links the records by storing the NAV number as the external ID.
The customer record is written to the NAV Customers endpoint — created on Add, or merged into the existing record on Update (a partial merge that does not clear unmapped fields).
The Microsoft Dynamics NAV customer number (No.) is retained as the external ID for future updates.

Mappings

Add/Update Microsoft Dynamics NAV Customer FROM iPaaS.com

iPaaS.com data type: Customer

Description. Writes the iPaaS.com customer to the Microsoft Dynamics NAV customer record. The Add and Update collections share the same field mappings; the only difference is that Add creates a new NAV customer while Update merges into the matching existing record (a partial merge — empty source values do not overwrite existing NAV data).

Mapping Type	Source Field (iPaaS.com)	Destination Field (Microsoft Dynamics NAV)	Description
Field	`CustomerNumber`	No	Key. Sets the NAV customer number and is the unique key used to link and update the record; must be present and unique. On Update it identifies the existing customer.
Field	`FirstName`	Name	Recommended. Sets the customer Name. As configured, maps from the First Name only.
Field	`Company`	Company_Name	Recommended. Sets the company name.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Address1")`	Address	Recommended. Street address from the primary billing address.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Address2")`	Address_2	Recommended. Secondary address line from the primary billing address.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "City")`	City	Recommended. City from the primary billing address.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Region")`	County	Recommended. Region (state/province) from the primary billing address.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "PostalCode")`	Post_Code	Recommended. Postal code from the primary billing address.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Country")`	Country_Region_Code	Recommended. Country/Region code from the primary billing address; must be a valid NAV Country/Region Code.
Dynamic Formula	`FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "PhoneNumber")`	Phone_No	Recommended. Phone number from the primary billing address.
Field	`EmailAddress`	E_Mail	Recommended. Customer email.

Error Handling

"CustomerNumber Duplicate Prefix preset is null/empty while CommaSeparated Customer CustomField Matching Name & Value preset has this value: \<value>" — The duplicate-matching custom-field setting is configured but the prefix setting is empty. Resolution: set the CustomerNumber Duplicate Prefix, or clear the matching setting.
For the full catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article.

Testing & Validation

Test Scenarios

Create a new customer in iPaaS.com and run the Add transfer; confirm the customer is created in Microsoft Dynamics NAV with the expected number, name, and primary billing address.
Update a field (for example, the email or address) on an existing customer and run the Update transfer; confirm the change appears in NAV and that unmapped fields are preserved.
Attempt a transfer for a customer whose NAV configuration is missing a required field (for example, a Customer Posting Group); confirm NAV returns a clear validation error.
Run a manual sync using the customer number and confirm the correct NAV customer is created or updated.
With the duplicate-matching settings configured, transfer a customer that already exists in NAV and confirm it links to the existing record rather than creating a duplicate.

Validation Checklist

The Customers web service is published in NAV with the exact service name Customers.
Required NAV customer fields are mapped or defaulted.
The duplicate-matching settings are either both set or both empty.
Primary billing address is present on customers that should carry address detail.

Additional Notes

The customer Name is sourced from the First Name only — see Known Limitations.
Companies are also written to the same NAV Customers endpoint through the separate Company From iPaaS.com collections.
For directionality, required web services, value-replacement, and environment-specific behaviors that apply across collections, see the Microsoft Dynamics NAV Known Limitations article.

iPaaS.com to Microsoft Dynamics NAV Customer Mapping Documentation