Summary
Microsoft Dynamics NAV locations can be captured into iPaaS.com through the Location To iPaaS.com mapping collection. NAV locations are polled on a schedule and created or updated as iPaaS.com locations with their name and description.
ID Format
Manual Sync ID Format. To capture a single location on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Location To iPaaS.com transfer, and enter the Microsoft Dynamics NAV location Code.
Pattern: the NAV location Code
Example:
MAIN
External ID Format. The Microsoft Dynamics NAV location Code is stored as the external ID on the iPaaS.com location, linking the two records.
Deleted Record Support
Not supported. The integration captures locations into iPaaS.com only; deleting a location in Microsoft Dynamics NAV is not captured and does not remove the location from iPaaS.com.
Custom Field Support
Custom fields are not supported for this collection.
Mapping Collection Status
Status: Enabled
Trigger Events: Automatic transfers are activated by the subscriber in the iPaaS.com subscription configuration's Inbound Data Flows section, by enabling this collection's events (Poll, Create, and Update). 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 affect the same record. No other mapping collection writes to the iPaaS.com location record; this is the only collection that captures locations.
Collision handling. Not applicable (configurable collision handling applies only to the Sales Order collections).
Duplicate Matching
A distinct mechanism: before creating an iPaaS.com location, the integration links to an existing iPaaS.com location matched by name to avoid creating a duplicate, storing the NAV location Code as the external ID.
Supported Child Collections
None.
System Caveats
Microsoft Dynamics NAV Caveats
The Locations OData web service must be published in Microsoft Dynamics NAV with the service name exactly
Locations, or locations cannot be polled.Locations are read from Microsoft Dynamics NAV; the integration does not create or modify locations in NAV.
iPaaS.com Caveats
A location captured into iPaaS.com is used as a reference record by other flows (for example, Product Inventory is recorded against an iPaaS.com location). Establish locations before relying on inventory transfers.
Setup Requirements
Microsoft Dynamics NAV Configuration
Publish the Locations OData web service (Departments → Administration → IT Administration → Services → Web Services), with the service name exactly
Locations. 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
The scheduled location poll requests locations from the Microsoft Dynamics NAV
Locationsendpoint.For each location, the integration links to an existing iPaaS.com location by name, or prepares a new one.
The location is created or updated in iPaaS.com with its name and description.
The NAV location Code is retained as the external ID for future updates.
Mappings
Add/Update Microsoft Dynamics NAV Location TO iPaaS.com
iPaaS.com data type: Location
Description. Captures a Microsoft Dynamics NAV location into the iPaaS.com location record. The iPaaS.com API also requires a related-to reference on the location, but the integration supplies this automatically; it is not a subscriber-supplied mapping.
Mapping Type | Source Field (Microsoft Dynamics NAV) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. iPaaS.com location name, from the NAV location Name. |
Field |
| Description | Recommended. iPaaS.com location description, from the NAV location Code. |
Error Handling
For the catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article.
Testing & Validation
Test Scenarios
Create a location in Microsoft Dynamics NAV and run the poll (or a manual sync by Code); confirm it appears in iPaaS.com with the expected name and description.
Rename a location in NAV and re-run; confirm the iPaaS.com location updates rather than creating a duplicate.
Run a manual sync using the NAV location Code and confirm the correct iPaaS.com location is created or updated.
Validation Checklist
The Locations web service is published in NAV with the exact service name
Locations.iPaaS.com locations carry the NAV location Code as their external ID.
Additional Notes
Locations are reference data for Product Inventory transfers (see the Product To iPaaS.com mapping documentation and the Default iPaaS Location Id For Inventory setting in Connections and Settings).
For directionality, required web services, and environment-specific behaviors that apply across collections, see the Microsoft Dynamics NAV Known Limitations article.