Summary
Microsoft Dynamics NAV shipping methods (shipping agents) can be captured into iPaaS.com through the Shipping Method To iPaaS.com mapping collection. NAV shipping agents are polled on a schedule and created or updated as iPaaS.com shipping methods with their name and description.
ID Format
Manual Sync ID Format. To capture a single shipping method on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Shipping Method To iPaaS.com transfer, and enter the Microsoft Dynamics NAV shipping agent Code.
Pattern: the NAV shipping agent Code
Example:
FEDEX
External ID Format. The Microsoft Dynamics NAV shipping agent Code is stored as the external ID on the iPaaS.com shipping method, linking the two records.
Deleted Record Support
Not supported. The integration captures shipping methods into iPaaS.com only; deleting a shipping agent in Microsoft Dynamics NAV is not captured and does not remove the shipping method 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 shipping method record; this is the only collection that captures shipping methods.
Collision handling. Not applicable (configurable collision handling applies only to the Sales Order collections).
Duplicate Matching
A distinct mechanism: before creating an iPaaS.com shipping method, the integration links to an existing iPaaS.com shipping method matched by name to avoid creating a duplicate, storing the NAV shipping agent Code as the external ID.
Supported Child Collections
None.
System Caveats
Microsoft Dynamics NAV Caveats
The ShippingAgents OData web service must be published in Microsoft Dynamics NAV with the service name exactly
ShippingAgents, or shipping methods cannot be polled.Shipping agents are read from Microsoft Dynamics NAV; the integration does not create or modify shipping agents in NAV.
iPaaS.com Caveats
The iPaaS.com shipping method Name is taken from the NAV shipping agent Code and the Description from the NAV Name (note the source fields are crossed relative to their labels).
Setup Requirements
Microsoft Dynamics NAV Configuration
Publish the ShippingAgents OData web service (Departments → Administration → IT Administration → Services → Web Services), with the service name exactly
ShippingAgents. 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 shipping method poll requests shipping agents from the Microsoft Dynamics NAV
ShippingAgentsendpoint.For each shipping agent, the integration links to an existing iPaaS.com shipping method by name, or prepares a new one.
The shipping method is created or updated in iPaaS.com with its name and description.
The NAV shipping agent Code is retained as the external ID for future updates.
Mappings
Add/Update Microsoft Dynamics NAV Shipping Method TO iPaaS.com
iPaaS.com data type: Shipping Method
Description. Captures a Microsoft Dynamics NAV shipping agent into the iPaaS.com shipping method record.
Mapping Type | Source Field (Microsoft Dynamics NAV) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. iPaaS.com shipping method name, from the NAV shipping agent Code. |
Field |
| Description | Recommended. iPaaS.com shipping method description, from the NAV shipping agent Name. |
Error Handling
For the catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article.
Testing & Validation
Test Scenarios
Create a shipping agent 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 shipping agent in NAV and re-run; confirm the iPaaS.com shipping method updates rather than creating a duplicate.
Run a manual sync using the NAV shipping agent Code and confirm the correct iPaaS.com shipping method is created or updated.
Validation Checklist
The ShippingAgents web service is published in NAV with the exact service name
ShippingAgents.iPaaS.com shipping methods carry the NAV shipping agent Code as their external ID.
Additional Notes
For directionality, required web services, and environment-specific behaviors that apply across collections, see the Microsoft Dynamics NAV Known Limitations article.