Summary
A Company To iPaaS.com mapping collection exists and is configured to capture company name and contact details from Microsoft Dynamics NAV into iPaaS.com. It is not active in this version — the integration registers no poll or webhook trigger for the company capture, so it does not run as a standalone transfer (see Mapping Collection Status and Known Limitations). Companies are written from iPaaS.com to Microsoft Dynamics NAV through the separate Company From iPaaS.com collections.
ID Format
Not applicable while the transfer is inactive. The Microsoft Dynamics NAV company is identified by its record number (No.), for example 00-1234.
Deleted Record Support
Not applicable (the capture is inactive).
Custom Field Support
Custom fields are not used by this collection.
Mapping Collection Status
Status: Configured but not active. No poll or webhook trigger is registered for the Customer Company type in the To iPaaS.com direction, and the To-iPaaS prerequisite handler does not create companies, so this collection does not run. See the Microsoft Dynamics NAV Known Limitations article.
Trigger Events: None registered.
Duplicate or Conflicting Mappings
Other collections that affect the same record. Companies are written to Microsoft Dynamics NAV through the Company From iPaaS.com collections (which use the NAV Customers endpoint). This To iPaaS.com collection would capture in the reverse direction if it were active.
Collision handling. Not applicable.
Supported Child Collections
None.
System Caveats
Microsoft Dynamics NAV Caveats
Even if the transfer were activated, the Customers OData web service would need to be published (companies are NAV customer records).
iPaaS.com Caveats
Because the transfer is inactive, companies do not flow from Microsoft Dynamics NAV into iPaaS.com. If company data is needed in iPaaS.com, it must originate there (it is then written to NAV via the Company From iPaaS.com collections).
Setup Requirements
No subscriber setup applies while the transfer is inactive.
Integration Flow
Not applicable — the collection does not execute in this version.
Mappings
Add Microsoft Dynamics NAV Company TO iPaaS.com
iPaaS.com data type: Customer Company
Description. The configured field mappings below would capture company name and contact details from Microsoft Dynamics NAV into iPaaS.com if the transfer were activated. They are inactive in this version.
Mapping Type | Source Field (Microsoft Dynamics NAV) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Company name (inactive). |
Field |
| EmailAddress | Company email (inactive). |
Field |
| PhoneNumber | Company phone number (inactive). |
Error Handling
Not applicable while the transfer is inactive. See the Microsoft Dynamics NAV Error Messages article for the integration's error catalog.
Testing & Validation
Test Scenarios
No functional test applies in this version. If the transfer is activated in a future release, validate that a NAV company is captured into iPaaS.com with the expected name, email, and phone.
Validation Checklist
Confirm with the integration team before relying on a NAV → iPaaS.com company transfer; it is not available in this version.
Additional Notes
This limitation is recorded in the Microsoft Dynamics NAV Known Limitations article and in the engineering flags for the integration. Company data flows iPaaS.com → NAV via the Company From iPaaS.com collections.