Integration Framework v2 allows you to integrate with both:
- Dynamics NAV 2013/2015/2016/2017/2018 installations
- Dynamics 365 Business Central On-Premise/Cloud installations.
Read more about how each feature is implemented on these systems below.
The Import Currencies feature imports currencies from NAV/Business Central with a name, a code, and an exchange rate. Currently, all currencies from NAV/Business are imported - for simple setups consider creating currencies manually instead.
The IsLCY field exists to inform you which currency is the baseline currency in the remote system - it does not have an equivalent field in DW, nor should it be imported.
Standard request:
Standard response:
The Import Languages feature imports languages from NAV with an ID, a language code, and a name.
Standard request:
Standard response:
Product units – e.g. pieces, boxes or boatloads – can also be imported and synchronized between the ERP and the Dynamicweb solution.
Standard request:
Standard response:
The Import Manufacturers feature imports all NAV vendors to Dynamicweb as manufacturers.
Standard request:
Standard response:
The Import Customers feature imports NAV Contacts as Dynamicweb Users, where they can then login, place orders, and generally behave like any other user. It can also import NAV Sales People as users, with data on which users they are allowed to impersonate.
Out of the box this request imports all NAV Contact Cards with a valid NAV Customer Card and places them in a Customers group – relevant information from the associated NAV Customer Card is stamped down on the users, e.g. a customer number, the company address, a currency code, and any ship-to addresses.
The parameter importSalesPeople causes the request to import all NAV Sales People as users in a Sales group. Associated NAV Contact Cards are imported to the AccessUserSecondaryRelation table in the database, which means that the NAV Sales People users will be able to impersonate these users and act on their behalf in frontend e.g. create orders, view order history, generate customer statement reports, etc.
As of Dynamicweb 9.10, the parameter importContacts allows you to control whether or not to import contacts. When set to false only customer records will be imported, which also means that addresses and alternative addresses for contacts will not be imported, only ship-to addresses associated with a customer.
importContacts is set to true by default.
If you want to include the Dynamicweb custom fields in the output of the response xml for this request then you need to configure the Business Central custom fields of type Contact when the importContacts = true (default) or Customer when importContacts = false. The custom fields setup is described here.
Standard request:
Standard Response
The basic structure of the XML response is this:
- A table containing the user group 'Customers'
- A table containing all NAV Contact Cards
- A table containing all NAV addresses
Here's an example containing one user and one address:
The Import Product Groups imports item categories from NAV/Business Central as Dynamicweb product groups. It also imports the following relational tables:
- EcomShopGroupRelation handles relations between groups and a shop
- EcomGroupRelation handles internal relations between groups
- EcomGroupProductRelation handles relations between groups and products
As described in the introduction, you should import product groups before you import products. If you don’t, please be aware that it is not usually practical to work with the products in Dynamicweb PIM unless you have a group structure to navigate.
NAV/Business Central does not contain translations for item categories – but you can still import them to more than one language using the languages parameter:
Parameter |
Values |
Required? |
Comments |
languages |
A comma-separated list of country codes |
No |
Defines which additional languages to create the groups in |
setLanguage | A country code | Yes |
Defines the language of the imported data – use system language from NAV, i.e. the language you enter data in. |
shopID | A shop id | No - but highly encouraged! |
Relates all imported groups to this specific shop or warehouse. |
Standard request
Standard response:
The Import Products feature imports items from NAV/Business Central as Dynamicweb products. Please note, that if you want to place the imported items in product groups or warehouse groups imported from a remote system, make sure you import the group structure before the products.
The importProductProperties attribute allows you to also import item properties from NAV/Business Central as product properties – they are placed in a product category called Imported NAV Item Attributes. This attribute includes a number of related tables, so mind the overhead.
If you have more than 1000 records when importing products we recommend using pagination - see the Import data with paging add-in documentation.
The following parameters can be used to control which languages to include in the import:
Parameter |
Values |
Required? |
Comments |
setLanguage |
A country code |
Yes |
Defines the language of the imported data – use system language from NAV, i.e. the language you enter data in. |
languages |
A comma-separated list of country codes |
No |
Defines which additional translations from NAV to also include in the import. |
groupID |
A group id | No |
Imports all products to this specific group - e.g. a New products group. Make sure this group exists and is associated with a shop or warehouse.
Usually only relevant for PIM setups where the warehouse structure should be built manually or imported from an different place than the ERP.
Set on the GetEcomData request. |
Standard request:
Standard response:
The Import Product Stock feature imports product stock from NAV to Dynamicweb. By default, stock is imported as a single summed number regardless of the inventory location, but a modifier – importStockLocations – allows you to import inventory per product per location.
Product stock is also imported (as a summed number) by the Import Products feature – but this feature is comparatively light weight and can be run more frequently without impacting performance.
Standard request:
Standard response:
The Import Countries feature imports countries from NAV/Business Central. Currently, all countries from NAV/Business are imported - for simple setups consider creating the required countried manually instead.
Standard request:
Standard response:
The Import Prices feature is used to – as the name implies – import prices from NAV/Business Central. In its most simple form the request simply returns base prices for all products, but you can use various parameters to import prices to the Price Matrix, which is a Dynamicweb feature for assigning different prices to a product based on variables like the product unit, the language id, or the currency type. It can also be used to store informative prices like a before-price.
This works in the following manner:
- The base request imports base prices directly to the EcomProducts table
- A parameterized requests will import base prices to EcomProducts and more specific prices to EcomPrices, where price matrix prices are stored
Let’s have some examples.
Scenario 1:
You want to import base prices in a specific currency – NOK – rather than the ERP base currency. Your request:
In response you get prices in NOK for all products. Since you’re requesting base prices they are imported to the EcomProducts table:
Scenario 2:
You want to run campaign prices for a while, based on the prices of a specific user with customer number 3000. You want to import this user’s prices in norwegian kroner (NOK) and using the norwegian language code (NOR). Your request:
In response you get the following:
- Customer-specific prices in the chosen currency in EcomProducts.ProductPrice
- Non-specific (“before”) prices in EcomProducts.ProductPriceBefore. This field does not exist on EcomProducts, but it is useful during development and you can of course map it to a custom product field, if you want to.
- Customer-specific prices in the chosen currency in EcomPrices.PriceAmount. This price is set to PriceIsInformative=false since it’s marked as the standard price.
- Non-specific prices in the chosen currency in EcomPrices.PriceAmount. This price is set to PriceIsInforative=true because it’s no longer valid, but it can be used as an Before-price in frontend.
Please note that the salesCode parameter can also take a Customer Price Group code as a value, retrieving group-specific prices instead of customer-specific prices. In a typical setup you will also have a specific D365/Nav customer for anonymous visitors, and you can use this to retrieve prices for more general B2C campaigns.
The export users feature makes it possible to export Dynamicweb users to NAV/Business Central as customers and contacts. This typically makes sense if your solution allows new customers to register on the website, or if you make it possible for a customer to register new contacts via the website.
When this feature is implemented:
- Users with no customer number are exported to NAV/BC as customers
- Users with an existing customer number are exported as contacts under the customer with that customer number
This means that you should ensure that when new user accounts are registered they have an appropriate value in the Customer number field if you want them to be exported as contacts. Please also keep in mind that NAV/BC does not contain standard fields for all standard Dynamicweb user fields – please see example request/response for the fields which are included by default.
When it comes to addresses:
- Addresses on a Dynamicweb user which is exported as a customer are created as ship-to addresses in NAV/BC.
- Addresses on a Dynamicweb user which is exported as a contact are treated in the following manner:
- If the address is present on the parent customer account & all other contacts under the parent it is created as an additional ship-to address on the customer in NAV/BC
- If the address is not present on all contacts & the parent customer it is created as an alternative address on the contact in NAV/BC
Standard request:
Standard response:
Export & Import Addresses
Please note, that when new addresses are exported from Dynamicweb to NAV/Business Central, you risk importing them again as duplicate data if your setup imports addresses from NAV/BC. To avoid this edit the import job and set the key settings for the field AccessUserAddress to AccessUserAddressUId AND AccessUserAddressUserId.
XML attributes are used by both batch integration add-ins and the live integration to trigger a particular behavior on the remote side or in the Connectors, such as batch sizes, reimports, and so on.
Some attributes may have to be added manually to your request, depending on the integration architecture.
Here is a (partial) list of attributes and what they are used for:
Attribute |
Values |
Use |
CustomModifier |
Any string |
When two instances of a website point to one remote instance, this attribute allows the data to be synchronized independently. |
If you wish to extend which columns are included in the reponses from Business Central you can configure custom fields for the following objects:
Item, Customer, Contact, Sales Header, Sales Line, Sales Invoice Header, Sales Invoice Line, Sales Cr.Memo Header, Sales Cr.Memo Line. |
Adding custom fields to entities imported from Business Central can be done with the Dynamicweb Custom Fields List or the Dynamicweb custom field configuration edit in D365 Business Central.
The easiest way to locate these pages is to use the search function in BC as depicted below.

To configure a custom field follow these steps:
- Open the Dynamicweb Custom Fields List page
- Select the table you wish to extend from the dropdown (A in the screenshot below)
- Select the field you wish to add - the field must be selected from the list - click the meatball menu (B) to do so
- Make sure the custom field is activated in the checkbox (C)

When you finished this setup the configured custom fields should be included in the response from Business Central.