Summary
iPaaS.com companies can be transferred into Microsoft Dynamics NAV through the Company From iPaaS.com mapping collections. Microsoft Dynamics NAV represents companies as customer records, so these collections write to the NAV Customers endpoint — the Add collection creates a new record and the Update collection refreshes an existing one.
ID Format
Manual Sync ID Format. To sync a single company on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Company From iPaaS.com transfer, and enter the iPaaS.com company Id. The integration writes this value as the Microsoft Dynamics NAV record number (No.).
Pattern: the iPaaS.com company Id
Example:
00-1234
External ID Format. After a successful sync, the Microsoft Dynamics NAV record number (No.) is stored as the external ID that links the iPaaS.com company to its NAV record.
Deleted Record Support
Outbound delete is not supported. The Company model's Delete method is not implemented, delete mappings are not included in the default templates, and company deletions in iPaaS.com do not propagate to Microsoft Dynamics NAV.
Custom Field Support
This collection supports custom fields. To populate a Microsoft Dynamics NAV 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. The name must be a valid 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 Company Add and Company Update From iPaaS.com collections both target the same Microsoft Dynamics NAV record. The Customer From iPaaS.com collections also write to the NAV Customers endpoint (NAV stores companies as customer records), so company and customer transfers share the same NAV table — keep iPaaS.com company Ids and customer numbers distinct so the two flows do not write to the same NAV record.
Collision handling. Configurable collision handling is not used for companies; it applies only to the Sales Order collections.
Duplicate Matching
A distinct mechanism from collision handling: before creating a company, the integration links to an existing Microsoft Dynamics NAV customer record whose number (No.) matches the iPaaS.com company Id, avoiding a duplicate. Unlike the Customer collections, company matching does not use the CustomerNumber Duplicate Prefix or CommaSeparated Customer CustomField Matching settings.
Supported Child Collections
None. Company address detail is mapped onto the record itself (see the Mappings section).
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 company 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.
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 company has an address flagged as the primary billing address.
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 company is sent from iPaaS.com to Microsoft Dynamics NAV (Add for a new record, Update for an existing one).
The integration checks for an existing NAV customer record by number (the iPaaS.com company Id); if found, it links the records by storing the NAV number as the external ID.
The record is written to the NAV
Customersendpoint — created on Add, or merged into the existing record on Update (a partial merge that does not clear unmapped fields).The Microsoft Dynamics NAV record number (No.) is retained as the external ID for future updates.
Mappings
Add/Update Microsoft Dynamics NAV Company FROM iPaaS.com
iPaaS.com data type: Customer Company
Description. Writes the iPaaS.com company to a Microsoft Dynamics NAV customer record. The Add and Update collections share the same field mappings; Add creates a new record while Update merges into the matching existing record (a partial merge — empty source values do not overwrite existing NAV data). The Update collection reuses the linked record's number as the matching key.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics NAV) | Description |
Dynamic Formula |
| No | Key. Sets/identifies the NAV record number. Add uses the iPaaS.com company Id; Update reuses the number already stored on the linked NAV record. |
Field |
| Name | Recommended. Company name. |
Dynamic Formula |
| Address | Recommended. Street address from the primary billing address. |
Dynamic Formula |
| Address_2 | Recommended. Secondary address line from the primary billing address. |
Dynamic Formula |
| City | Recommended. City from the primary billing address. |
Dynamic Formula |
| County | Recommended. Region (state/province) from the primary billing address. |
Dynamic Formula |
| Post_Code | Recommended. Postal code from the primary billing address. |
Dynamic Formula |
| Country_Region_Code | Recommended. Country/Region code from the primary billing address; must be a valid NAV Country/Region Code. |
Dynamic Formula |
| Phone_No | Recommended. Phone number from the primary billing address. |
Field |
| E_Mail | Recommended. Company email. |
Error Handling
For the catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article. NAV rejects a company write when a required customer field is missing in the target company configuration; the error names the field.
Testing & Validation
Test Scenarios
Create a new company in iPaaS.com and run the Add transfer; confirm a NAV customer record is created with the expected number, name, and primary billing address.
Update a field on an existing company and run the Update transfer; confirm the change appears in NAV and that unmapped fields are preserved.
Attempt a transfer for a company whose NAV configuration is missing a required field; confirm NAV returns a clear validation error.
Run a manual sync using the company Id and confirm the correct NAV record is created or updated.
Validation Checklist
The Customers web service is published in NAV with the exact service name
Customers.Required NAV customer fields are mapped or defaulted.
Primary billing address is present on companies that should carry address detail.
Additional Notes
Companies and customers share the NAV
Customersendpoint; see also the Customer From iPaaS.com mapping documentation.For directionality, required web services, and environment-specific behaviors that apply across collections, see the Microsoft Dynamics NAV Known Limitations article.