D365 Field Service and NAV Integration
Supports:
SmartConnect 2017+
SmartConnect 2017+
Publisher:
eOne Solutions
eOne Solutions
D365 Field Service and NAV Integration
Overview
The Dynamics 365 Field Service and Dynamics NAV templates provide an excellent base for any integration that is designed to connect these two system together. The templates are designed to sync the needed master records from Dynamics NAV to Dynamics 365 Field Service, and then to push any transactions from D365 Field Service to Dynamics NAV when the user chooses.
There are integration points for the following records:
Any of the mappings can be changed or configured once the integrations are imported into SmartConnect, so additional fields can be included or even new maps can be added to fit specific needs.
There are integration points for the following records:
- Accounts
- Territories
- Warehouses
- Inventory
- Associated Inventory Records – Currencies, Unit of Measures
- Invoices
- Purchase Orders
Any of the mappings can be changed or configured once the integrations are imported into SmartConnect, so additional fields can be included or even new maps can be added to fit specific needs.
Details
General Information
The Dynamics 365 Field Service and Dynamics NAV templates consist of a collection of pre-configured maps. There are integration points for the following records:
Prerequisites
Prerequisites to using these templates are as follows:
Step 1: Implement the Needed Customizations to Dynamics 365 Field Service
There are a set of custom attributes that need to exist within Dynamics 365 Field Service in order for the transaction-based integrations to run correctly. There are 2 custom attributes that are needed on each of the Invoice, Purchase Order, Inventory Adjustment, and Inventory Transfer entities. The attribute display and technical names are the same on each of the entities, and are listed below:
Step 2: Publish the needed web services with Dynamics NAV / 365 Financials
SmartConnect makes use of web service endpoints within Dynamics NAV / 365 Financials. These web services need to be published before the maps can be imported successfully.
When the services are published, the Dynamics NAV Web Services window will look similar to the following image (depending what other services are already published):
Step 3: Import and Configure the Dynamics 365 Field Service – Dynamics NAV Maps
Template Map Details
There are multiple different types of maps that are included in the templates. This section will categorize and assist in determining which each set of integrations should run. The bulk maps that can be run during the initial setup from Dynamics NAV to Dynamics 365 Field Service are as follows:
Final Steps
The Dynamics 365 Field Service and Dynamics NAV templates consist of a collection of pre-configured maps. There are integration points for the following records:
- Accounts
- Territories
- Warehouses
- Inventory
- Associated Inventory Records – Currencies, Unit of Measures
- Invoices
- Purchase Orders
Prerequisites
Prerequisites to using these templates are as follows:
- Have a valid Dynamics NAV/365 Financials and Dynamics 365 Field Service instance/organization
- SmartConnect 20.16.1.24 or higher installed and registered
- Your Dynamics 365 environment is already configured in the Dynamics CRM Connector within SmartConnect
- The Dynamics CRM Connector will connect to versions of Microsoft Dynamics CRM (4.0, 2011, 2013, 2015, and 2016), Dynamics 365 Sales, Customer Service, Project Service, and Field Service.
Step 1: Implement the Needed Customizations to Dynamics 365 Field Service
There are a set of custom attributes that need to exist within Dynamics 365 Field Service in order for the transaction-based integrations to run correctly. There are 2 custom attributes that are needed on each of the Invoice, Purchase Order, Inventory Adjustment, and Inventory Transfer entities. The attribute display and technical names are the same on each of the entities, and are listed below:
- Send to ERP eone_sendtoerp
- ERP Trx Number eone_erptrxnumber
Step 2: Publish the needed web services with Dynamics NAV / 365 Financials
SmartConnect makes use of web service endpoints within Dynamics NAV / 365 Financials. These web services need to be published before the maps can be imported successfully.
- Navigate to the Web Services window within Dynamics NAV / 365 Financials
- Click the New button to add a new published service to the list
- The services that are needed are as follows, make sure to have the correct Object ID and Service Name entered for each endpoint:
Object Type | Object ID | Object Name | Service Name |
Page | 21 | Customer Card | CustomerCard |
Page | 28 | Vendor Card | VendorCard |
Page | 30 | ItemCard | ItemCard |
Page | 5 | Currencies | Currencies |
Page | 429 | Territories | Territories |
Page | 209 | Units of Measure | Units_of_Measure |
Page | 15 | Location List | Location_List |
Page | 43 | Sales Invoice | SalesInvoice |
Page | 40 | Item Journal | ItemJournal |
Page | 50 | PurchaseOrder | PurchaseOrder |

Step 3: Import and Configure the Dynamics 365 Field Service – Dynamics NAV Maps
- Click on the “Maintenance” tab within SmartConnect
- Click the “Import Wizard” button within the SmartConnect Maintenance section
- Select the “FieldService_NAV_Maps.sce” file and import its contents
- During the import process, the map connections will need to be updated to point to the correct Field Service CRM and Dynamics NAV instances
- If the Connectors are already correctly setup within SmartConnect then the option to default the connection information from Setup option can be used

Template Map Details
There are multiple different types of maps that are included in the templates. This section will categorize and assist in determining which each set of integrations should run. The bulk maps that can be run during the initial setup from Dynamics NAV to Dynamics 365 Field Service are as follows:
- FS_NAV_TO_CRM_CURRENCIES_BULK
- FS_NAV_TO_CRM_TERRITORIES_BULK
- FS_NAV_TO_CRM_ACCOUNTS_BULK
- FS_NAV_TO_CRM_WAREHOUSES
- FS_NAV_TO_CRM_UOFM_BULK
- FS_NAV_TO_CRM_ITEMS_BULK
- FS_NAV_TO_CRM_PRICELISTITEMS_BULK
- FS_CRM_TO_NAV_INVOICES_BULK
- FS_CRM_TO_NAV_PURCHASEORDERS_BULK
- FS_NAV_TO_CRM_WAREHOUSES_ONGOING
- FS_NAV_TO_CRM_TERRITORIES_ONGOING
- FS_NAV_TO_CRM_ACCOUNTS_ONGOING
- FS_NAV_TO_CRM_CURRENCIES_ONGOING
- FS_NAV_TO_CRM_UOFM_ONGOING
- FS_NAV_TO_CRM_ITEMS_ONGOING
- FS_CRM_TO_NAV_ACCOUNTS_ONGOING
- FS_CRM_TO_NAV_INVOICES_ONGOING
- FS_CRM_TO_NAV_PURCHASEORDERS_ONGOING
- FS_CRM_TO_NAV_VENDORS_PRE_PO
- Pre map task on both bulk and ongoing purchase order map
- Ensures account exists as a vendor in Dynamics NAV
- FS_NAV_TO_CRM_INVOICE_CALLBACK
- Post map task on both bulk and ongoing invoice map
- Updates the ERP Trx Number attribute with document number from Dynamics NAV
- FS_NAV_TO_CRM_PURCHASEORDER_CALLBACK
- Post map task on both bulk and ongoing purchase order map
- Updates the ERP Trx Number attribute with document number from Dynamics NAV
Final Steps
- Schedule the maps that have the suffix of _ONGOING on whatever schedule is desired
- A 5-minute interval should be the quickest timeframe in which the maps are set to repeat, as this will allow each integration to complete before starting the cycle again
- Determine which of the maps are actually required for a particular implementation
- Add in any desired error logging and alerts
- Common steps involve turning on the Log Errors flag in the Options tab of the Map Setup screen for any particular map, and setting up emails to send on the failure of an integration using the Map Tasks