Before You Begin
Before installing the integration, you need to perform configuration steps in Microsoft Dynamics NAV.
In the Windows Client, go to Administration > IT Administration > General.
Copy the User Name.
Ask the user for their password.
If NAV is configured with Windows Authentication auth type, the password is managed by the network.
If the user doesn't know, it must be reset by an IT administrator via Active Directory.
Open the Windows Client and enter the User Name and Password.
Navigate to Web Services.
Next, add OData Web Service Endpoints in Microsoft Dynamics NAV.
Go to [Company Name]> Departments > Administration > IT Administration > Services > Web Services. You can also search for Web Services in the search bar.
A list of existing web services is displayed.Click New to add a new web service. The New - Wb Services page is displayed.
Enter the following details in the empty row.
Object Type (Page)
ID
Name
Service
OData URL
Save the new web service.
Once the details are entered, the new web service will be added.
List of Used Web Service Endpoints:
Service Name | Object Name |
Items | Item Card |
SalesOrders | Sales Order |
Customers | Customer Card |
SalesOrderLines | Lines |
ShippingAgents | Shipping Agents |
Locations | Location Card |
NOTE: The service name must exactly match as above against each object name for proper configuration and functionality. The OData URL must be in the following format:
The service name can be extracted from the table above, against each object name selected. |
Installation Instructions for Integration Setup
Go to Subscriptions Management > Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the Microsoft Dynamics NAV Integration title.
On the Subscription Detail page, click the Subscribe button.
Enter the name of the subscription and select a version. It can be set to any relevant and unique subscription name within the company where this subscription is created.
Format: [Product Name] - [Environment/Purpose]
Example: MSDNAV – Release
Select Create Default Mappings (recommended)
NOTE: If you don’t want to create default mappings and want to create all mappings from scratch by yourself, then uncheck this box. |
Provide the API URL from your Microsoft Dynamics NAV instance. The format is:
https://[your-instance].[product-domain].com:portEnter the Domain associated with your NAV server.
Enter the NAV Company Name as configured in your Microsoft Dynamics NAV instance.
Enter the Environment of your Microsoft Dynamics NAV instance.
Enter the OData Version of NAV APIs.
Enter values for the following fields:
General Polling SettingsTransaction Poll Search Days: This setting specifies the number of days of transaction data to fetch from NAV during the initial data pull. It controls how far back the system looks into the transaction history.
Default iPaaS Location ID for Inventory: This is a required setting because the NAV Product API does not include a specific location field for inventory. The system needs this ID to manage product inventory data efficiently. You can find it in Departments > Administration > Application Setup > Warehouse > Locations.
Poll Time UTC Adjustment: Use this to adjust polling to align with the time zone of your NAV server. A standard setting is 0 hours, but you can use an offset that matches your local NAV server's time zone.
Product PollingProduct Poll Search Days: This determines how many days of product history are queried on the initial run.
Recommended Values:
Initial Setup: 15-20 days
Ongoing Operations: 5 days
High Volume: 1-2 days
Product Poll Page Size: This defines the number of records returned per API call when polling product data.
Recommended Values:
Initial Setup: 200-500 records
Ongoing Operations: 100-200 records
High Volume: 50-100 records
Product Poll Date Time Field Override: This specifies the NAV field used to determine the last updated product records.
Recommended Values:
Default: Last Modified Date/Time
Alternative: Created Date (if Last Modified isn't available)
Recalculate $0 Price: When enabled, the system recalculates product pricing if NAV returns $0 values.
Recommended Values:
Enable: If NAV regularly sends placeholder $0 values.
Disable: If you do not use $0 as a placeholder.
Product Inventory PollingProduct Inventory Poll Search Days: This specifies how many days of inventory history are queried on the initial run.
Recommended Values:
Initial Setup: 15-20 days
Ongoing Operations: 5-7 days
High Volume: 1-2 days
Product Inventory Poll Date Time Field Override: This specifies the NAV field used to determine the last updated inventory records.
Recommended Values:
Default: Last Modified Date/Time
Alternative: Posting Date or Entry Date
Post-Installation Verification
After completing the installation, verify the integration by:
Connection Test: Verify firewall rules and API credentials.
Data Sync Test: Check NAV Job Queue logs and external system logs.
Functionality Test: Ensure all required NAV objects are imported.
Steps for Whitelisting the API (On-Premises machine)The IT provider will be responsible for carrying out this task and ensuring that the required IP addresses are allowed by using the following steps:
iPaas.com will send traffic from these IP addresses: outbound.iPaaS.com/52.184.255.108 (iPaaS.com production environment) 69.61.66.128/27 (iPaaS.com staging environment) |
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact Support or to search our documentation.
Documentation: API Introduction
Support Portal: https://support.ipaas.com/en/
Contact Information: Contact iPaaS.com