OData V4 object types - Import and export

This page contains documentation on how the OData provider of Dynamicweb handles each specific object type and how to set up integration activities for them.

Navigate to a specific object type by clicking it in the tabel of contents in the right side of the page.

To import countries from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the OData v4 URL in Business Central Web Services (see below)
• Provide the endpoint with a Name and an optional Description.
• Insert OData v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service:

Figure 2.1 Business Central Web service exposing Page 10 Countries/Regions as ODataV4 endpoint.

When importing countries, it is likely that Business Central has more records of the entity than you wish to import. To avoid importing unwanted countries to Dynamicweb, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

This example filters the OData so that it only includes records where the value of the code attribute is equal to either ‘DK’, ‘DE’ or ‘GB’.

For a full documentation on Business Central OData filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint (GET Countries) from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Country) from the dropdown menu in Parameters > destination > object type.
• Select the destination language in Dynamicweb.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In the activity settings view, the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of countries, the mappings should look like this:

*Manipulates the attribute by replacing the following values:

The updated value is then added to both EcomCountries.CountryAddressDisplayFormat and EcomCountries.CountryAddressEditFormat.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import currencies from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the OData v4 URL in Business Central Web Services (see below)
• Provide the endpoint with a Name and an optional Description.
• Insert OData v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service:

Figure 6.1 Web service exposing Page 15 currencies as ODataV4 endpoint.

When importing countries, it is likely that Business Central has more records of the entity than you wish to import. To avoid importing unwanted countries to Dynamicweb, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

This example filters the OData so that it only includes records where the value of the code attribute is equal to either ‘DKK’, ‘EUR’ or ‘USD’. Resulting in only Euro, Danish krone and US dollar being imported.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (currency) from the dropdown menu in Parameters > destination > object type.
• Select the destination language in Dynamicweb.
• Choose the default currency of Dynamicweb. Please notice that the base currency of Business Central has to match the default currency of Dynamicweb.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of currencies, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import user salespersons from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service:

Figure 10.1 Web service exposing Page 5116 User Salesperson as ODataV4 endpoint.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (User salesperson) from the dropdown menu in Parameters > destination > object type.
• Select the User group you want the imported records to be added to. The selected group will function as a parent group for the user salesperson, user and user customer object types. These will be automatically added as children to the selected parent group by Dynamicweb.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

The relation between customer and sales person in D365BC will be replicated in Dynamicweb so the sales person-based user account can impersonate each customer or contact-based user account in Dynamicweb.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of user salesperson, the mappings should look like this:

*The E_Mail value is added to both AccessUser.AccessUserUserName and AccessUser.AccessUserEmail.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import users from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service:

Figure 13.1 Web service exposing Page 5050 Contact Card as ODataV4 endpoint

When importing users, you might not wish to import all existing users/contacts in the ERP. To avoid importing unwanted users to Dynamicweb, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

The first example filters the OData so that it only includes records where the value of the contact no. of Business Central starts with the string ‘E01’.

The second example restricts the endpoint to only importing the first 20 records.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (User) from the dropdown menu in Parameters > destination > object type.
• Select the User group you want the imported records to be added to. The selected group will function as a parent group for the user salesperson, user and user customer object types. These will be automatically added as children to the selected parent group by Dynamicweb.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

Each contact imported will get a user account where the customer number matches the customer number of the company which each contact is associated to.

In the activity settings menu view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of user, the mappings should look like this:

*Since Dynamicweb uses the Salesperson_code key of the User object type for the purpose of impersonation. The endpoint provider checks if there are any user salespersons in the database with this ID. If so, the User Salesperson can then act on behalf of the User.   

**The E_Mail value is added to both AccessUser.AccessUserUserName and AccessUser.AccessUserEmail.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import user customers from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service:

Figure 17.1 Web service exposing Page 21 Customer Card as ODataV4 endpoint

When importing users, it is likely that Business Central has more records of the entity than you wish to import. To avoid importing unwanted user customers to Dynamicweb, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

The first example filters the OData so that it only includes records where the value of the customer no. of Business Central starts with the string ‘E01’.

The second example restricts the endpoint to only importing the first 20 records.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select the predefined endpoint from the dropdown menu.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (User Customer) from the dropdown menu in Parameters > destination > object type.
• Select the User group you want the imported records to be added to. The selected group will function as a parent group for the user salesperson, user and user customer object types. These will be automatically added as children to the selected parent group by Dynamicweb.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

Each customer imported will get a user account. These accounts could be used for frontend access to the customer center. This way one B2B customer gets one B2B user account. It is, however, best practice to use the contact-based user accounts. This way one B2B customer can have multiple B2B user accounts.

The company address of the B2B customer is also mapped to the contact-based B2B user accounts.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of user customer, the mappings should look like this:

*The No attribute value is added to both AccessUser.AccessUserCustomerNumber and  AccessUser.AccessUserExternalId

**The E_Mail value is added to both AccessUser.AccessUserUserName and AccessUser.AccessUserEmail.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

When importing User Customers the OData provider will look for any values in either the Customer_Price_Group or Customer_Discount_Group fields. 

If the imported records contain any values in these fields, the groups will be added as subgroups to their relevant User Groups in Dynamicweb.

Any subgroup is added with the name of either "Price_" or "Discount_" + the name of the group.

For example, an imported User Customer with a value of "Favorites" in the Customer_Discount_Group field will add a subgroup with the name of "Disc_Favorites" in Dynamicweb Users.

To import user addresses from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the User Address OData V4 URL:

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (User address) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of user address, the mappings should look like this:

*The value of code is added to both AccessUserAddress.AccessUserAddressName and AccessUserAddress.AccessUserAddressCallName.

To import user customer ship-to addresses from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the User customer ship-to address OData V4 URL:

Figure 25.1 Web service exposing 300 Ship-to address as ODataV4 endpoint.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (User customer ship-to address) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of user, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import manufacturer from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData V4 URL for manufacturers:

Figure 28.1 Web service exposing Page 26 Vendor Card as ODataV4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Manufacturer) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of manufacturer, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import stock locations from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 31.1 Web service exposing Page 15 Locations as ODataV4 endpoint

When importing stock locations, you might not be interested in importing all locations available in the ERP. To avoid importing unwanted locations to Dynamicweb, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

The first example filters the OData so that it only includes records where the value of the code attribute is equal to either ‘Location A’ or ‘Location B’.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Stock location) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of stock location, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To product groups from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product group) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product group, the mappings should look like this:

*The Parent_Category value is used to create relations between product groups and product group parents. If the parent category already exists in the database, the imported product group will be added as a child to this parent group. If the parent group does not already exist, it will be added to the database.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import products from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 38.1 Web service exposing Page 30 Item card as OData v4 endpoint

When importing products, you might not be interested in importing all listed products in the ERP. To avoid importing unwanted products to Dynamicweb, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

This example filters the OData so that it only includes records where the value of the No attribute starts with the string ‘OFS-‘.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product) from the dropdown menu in Parameters > destination > object type.
• Choose the desired shop to import products into.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product, the mappings should look like this:

*If no product group destination is manually selected in the integration activity settings, the import job will refer to this attribute to detemine in which group the product is placed. If the group does not already exist in the database, it will be added upon running the activity. 

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import product variants from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 42.1 Web service exposing Page 5401 Item variants as OData v4 endpoint

When importing product variants, you might not be interested in importing all listed variants in the ERP. To avoid importing unwanted product variants (such as those corrensponding to products not listed in Dynamicweb), a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

This example filters the OData so that it only includes records where the value of the Item_No attribute starts with the string ‘OFS-‘.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product variant) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product variant, the mappings should look like this:

*The value of Item_No is used to identify the master product that the variant belongs to. To do this, the OData provider establishes an ExtentedVariant attribute for the object. The Item_No and Code attributes are then used in combination as the value in EcomProducts.ProductVariantId  and Item_Code is also used as the value in EcomProducts.ProductNumber.

**Description is used as value for the EcomProducts.ProductName column.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import product units from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 46.1 Web service exposing Page 209 Units of measure as OData v4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product unit) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product unit, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import product-unit relations from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 49.1 Web service exposing Page 5404 Item units of measure as OData v4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product-unit relation) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product-unit relation, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

Product translations can be imported with the OData provider and Endpoint provider one language at a time.

If you want to import multiple translations for each product, you will therefore need to set up an endpoint and an integration activity for each of them.

Follow the step by step guide for each language: 

To import product translations from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description. Ideally, the name and description should fit the nature of the import. i.e. "GET German product translations from BC"
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 52.1 Web service exposing Page 35 Item translations as OData v4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product translation) from the dropdown menu in Parameters > destination > object type.
• Choose the destination language of the imported translations.
• Provide the Source Language Code. This has to match the language code of the ERP. For example, if you want to import german translations for Business Central, the Source Language Code is "DEU".
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product translation, the mappings should look like this:

*) Item translations endpoint in Business Central contains translations for both items and variants. The same endpoint also contains translations in many language codes. For those reasons, the source data needs to be filtered and transformed. The OData Provider handles this and ensures the expected translations in the expected language codes are placed in the correct Dynamicweb tables.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

Product unit translations can be imported with the OData provider and Endpoint provider one language at a time.

If you want to import multiple translations for each product, you will therefore need to set up an endpoint and an integration activity for each of them.

Follow the step by step guide for each language: 

To import product unit translations from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description. Ideally, the name and description should fit the nature of the import. i.e. "GET German product unit translations from BC"
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 55.1 Web service exposing Page 5402 Unit of Measure Translation as OData v4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Product unit translation) from the dropdown menu in Parameters > destination > object type.
• Choose the destination language of the imported prodcut unit translations.
• Provide the Source Language Code. This has to match the language code of the ERP. For example, if you want to import german translations for Business Central, the Source Language Code is "DEU".
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of product unit translation, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import stock amounts from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 58.1 Web service exposing Page 5700 Stockkeeping Unit Card as OData v4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Stock amount) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of stock amount, the mappings should look like this:

*) The OData Provider ensures that stock amount per location per variant per product in the base unit of measure is added to the stock matrix of a Dynamicweb product or master product.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import orders from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData v4 URL:

Figure 61.1 Web service exposing Page 42 Sales Order as OData v4 endpoint

When importing orders, you might not be interested in importing all listed orders in the ERP. To avoid importing unwanted records, a filter can be applied to the endpoint by adding a query parameter.

A query parameter consists of a key value pair and could look like the following example:

The first example filters the OData so that it only includes records where the value of the sell_to_Country_Region_Code is equal to the string ‘GB’. Resulting in the endpoint only exposing orders made to customers in Great Britain.

The second example restricts the endpoint to only importing the first 20 records of the entity.

For a full documentation on Business Central API filters click here.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select "OData V4 - Business Central" as Endpoint_Type 
• Select the predefined endpoint from the dropdown menu.
• Select the desired activity Mode at Advanced activity settings.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Stock amount) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb. Notice that there are two tables available: DynamicwebSalesOrder and DynamicwebSalesOrderSalesLines. The DynamicwebSalesOrderSalesLines table must be targeted to ObjectTypeOrderLines.
• Click finish.
• Finally, provide the activity with a name and an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In this view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

The order object type and underlying logic is more complex relative to the others. It can consume two overall entities: Sales orders and posted (invoiced) sales orders. It detects which endpoint it is automatically. No matter which entity, it is only the endpoint containing the order headers which is needed. From the header endpoint, the order object type logic automatically navigates to the underlying endpoint containing order lines.

Apart from this complexity, the order object type logic also maps entity properties in more than one table in Dynamicweb and combines multiple fields. This is visible in the mapping tables below where the Dynamicweb Destination column lists many “Handled by ObjectTypeOrder” and “Handled by ObjectTypeSalesLine”.

Mappings for DynamicwebSalesOrderSalesLines entity:

*No is used to fetch Order lines from BC.

**Posting_Date and Order_Date are fetched from two different entities in BC (PostedSalesInvoice and SalesOrder). They are used collectively in EcomOrders.OrderCompletedDate and EcomOrders.OrderDate).

***From the DynamicwebSalesOrderSalesLines entity the attributes of No, Variant_code, description, Quantity, Unit_price, Line_Discount_percent, Line_Amount, Line_Discount_Amount, and Total_VAT_Amount are all used to calculate prices, VAT and discounts and post them to the order in Dynamicweb.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import discounts from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the OData V4 URL:
 

Figure 65.2 Web service exposing Page 7004 Sales Line Discounts as ODataV4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select the Endpoint type
• Select the predefined endpoint from the dropdown menu.
• Choose an integration activity mode.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Discount) from the dropdown menu in Parameters > destination > object type.
• Choose the desired destination language and shop.
• Provide the activity with a discount Prefix. A prefix is a mandatory addition to the name of the discount and will appear on all discounts imported to Dynamicweb. Ideally, it should reflect the context of the imported discounts (E.G. “Summer sale 2021”).
• Select whether or not you want Dynamicweb to merge discounts if they are evaluated to be identical.*
• Select the Sales Types you wish to import.** 
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

*Business Central keeps discount records as individual records for every product with an applied discount. By allowing Dynamicweb to merge discounts it will store a discount as a single record with a list of all included products. It does so by checking the database for existing discount records that match the following attributes: UserId, ValidFrom, ValidTo, ShopId, LanguageId, Percentage, ProductQuantity, CurrencyCode. If a matching discount is found, the [code,code+variant_code] or [code,] value (depending on wether the product has a specified variant) is added to the list of products in EcomDiscount.DiscountProductsAndGroups.

**The OData provider supports import of three distinct types of discounts: Customer (discounts defined for individual customers), Customer discount groups (discounts specific for a defined group of customers) and discounts for All Customers. Check the boxes next to the types you wish to import. Multiple types can be imported simultaneously and at least one of the check boxes must be checked. 

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of discount, the mappings should look like this:

¹Code and Variant_Code is used in combination in the EcomDiscount.DiscountProductsAndGroups column. The combined code+variant_code attribute is only added to the endpoint if Variant_Code has a value in the endpoint.

²The external ID of SalesCode is used to locate AcessUsers in the Dynamicweb database. The located value in AccessUser.AccessUserId is used in EcomDiscount.DiscountAccessUserId.

³The attributes of Unit_of_Measure_Code and Minimum_Quantity are used to calculate the ratio between the two. The ratio is stored in EcomDiscount.DiscountProductQuantity. 

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import prices from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Locating the OData V4 URL:

Figure 68.2 Figure 1 Web service exposing Page 7002 Sales Prices as ODataV4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select the Endpoint type
• Select the predefined endpoint from the dropdown menu.
• Choose an integration activity mode.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Price) from the dropdown menu in Parameters > destination > object type.
• Choose the desired destination language and shop.
• Select the Sales Types you wish to import.* 
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

*The OData provider supports import of three distinct types of prices: Customer (prices defined for individual customers), Customer groups (prices specific for a defined group of customers) and prices for All Customers. Check the boxes next to the types you wish to import. Multiple types can be imported simultaneously and at least one of the check boxes must be checked. 

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of price, the mappings should look like this:

*Variant_Code is used in EcomPrices.PriceProductVariantID.

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To import prices and discounts from Business Central to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Locate and copy the Odata v4 URL in Business Central Web Services
• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central Web Services.
• Append "Lines" to the located URL - for example, if your Business Central web service is called MySalesPriceList the URL inserted should end with MySalesPriceListLines
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Locating the OData V4 URL:

Figure 71.2 Figure 1 Web service exposing Page 7016 Sales Price List as ODataV4 endpoint

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select the Endpoint type
• Select the predefined endpoint from the dropdown menu.
• Choose an integration activity mode.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Price and Discount) from the dropdown menu in Parameters > destination > object type.
• Choose the desired destination language and shop.
• Optionally, you can add a prefix to all imported discounts
• Select if you want to merge compared discounts*
• Click next.
• Check the Source checkbox to choose the target tables. The Business Central tables will be automatically mapped to the corresponding tables in Dynamicweb.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

*When merging compared discounts is enabled, DiscountProductAndGroups are added as a list of ID's in a single record instead of as individual records.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of price, the mappings should look like this:

*Product_No is used in combination with the variant_no requested from Business Central to PriceProductId og DiscountProductId

**Starting_date is mapped to either EcomPrices.PriceValidFrom or EcomDiscount.DiscountValidFrom depending on the source 

*** If the source object doesn't contain a Currency_Code, the destination column defaults to the default currency of the DynamicWeb solution.

****Ending_date is mapped to either EcomPrices.PriceValidTo or EcomDiscount.DiscountValidTo depending on the source 

To finish the activity setup, press save and close or save and run to perform the import job immediately.

By choosing the Custom object type in the OData provider, you can expose any ODataV4 Web service and create your own mapping in Dynamicweb OData Provider. In this case the OData Provider will delegate to Dynamicweb Provider.

To import custom object types to Dynamicweb, the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL of the desired web service. 
• Set Type to GET
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “Endpoint provider”.
• Select the predefined endpoint from the dropdown menu.
• Click next.
• For the Target setting choose Type: “OData provider”.
• Select the desired Object Type (Custom) from the dropdown menu in Parameters > destination > object type.
• Click next.
• Check the Source checkbox to choose the destination entities. The entities exposed by the web service will be visible.
• Choose the target entity in Dynamicweb for each exposed source entity. Since no auto-mappings are made for custom OData v4 web services and the OData provider delegates to the Dynamicweb provider, you can choose between all the entities of Dynamicweb.
• Click finish.
• Finally, provide the activity with a name and an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

To export user customers from Dynamicweb to Business Central the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central (see below).
• Set Type to POST.
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service URL:

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “OData”.
• Choose the source object type (User customer) from the dropdown menu.
• Select the Source user group you want to export records from.
• Click next.
• For the Target setting choose Type: “Endpoint provider”.
• Select the desired predefined Destination Endpoint from the dropdown menu at "parameters"
• Click next.
• Check the Source checkbox to choose the target tables. The Dynamicweb tables will be automatically mapped to the corresponding tables in Business Central.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of User customer, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To export users from Dynamicweb to Business Central the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central (see below).
• Set Type to POST.
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service URL:

Figure 79.1 Web service exposing page 5050 Contact Card as ODataV4 endpoint.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “OData”.
• Choose the source object type (User) from the dropdown menu.
• Select the Source user group you want to export records from.
• Click next.
• For the Target setting choose Type: “Endpoint provider”.
• Select the desired predefined Destination endpoint from the dropdown menu at “parameters”.
• Click next.
• Check the Source checkbox to choose the target tables. The Dynamicweb tables will be automatically mapped to the corresponding tables in Business Central.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of User, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To export user addresses from Dynamicweb to Business Central the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central (see below).
• Set Type to POST.
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service URL:

Figure 82.1 Web service exposing page 5056 Contact Alt. Address Card as ODataV4 endpoint.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “OData”.
• Choose the source object type (User address) from the dropdown menu.
• Select the Source user group you want to export records from.
• Click next.
• For the Target setting choose Type: “Endpoint provider”.
• Select the desired predefined Destination endpoint from the dropdown menu at “parameters”.
• Click next.
• Check the Source checkbox to choose the target tables. The Dynamicweb tables will be automatically mapped to the corresponding tables in Business Central.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of User, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To export user addresses from Dynamicweb to Business Central the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central (see below).
• Set Type to POST.
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service URL:

Figure 85.1 Web service exposing page 300 Ship-to Address as ODataV4 endpoint.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “OData”.
• Choose the source object type (User customer ship-to address) from the dropdown menu.
• Select the Source user group you want to export records from.
• Click next.
• For the Target setting choose Type: “Endpoint provider”.
• Select the desired predefined Destination endpoint from the dropdown menu at “parameters”.
• Click next.
• Check the Source checkbox to choose the target tables. The Dynamicweb tables will be automatically mapped to the corresponding tables in Business Central.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

For the object type of User customer ship-to address, the mappings should look like this:

To finish the activity setup, press save and close or save and run to perform the import job immediately.

To export orders from Dynamicweb to Business Central the endpoint for the purpose must first be added in settings > integration > endpoint management > add endpoint.

To add the endpoint, follow these steps:

• Provide the endpoint with a Name and an optional Description.
• Insert Odata v4 URL from Business Central (see below).
• Set Type to POST.
• Choose Endpoint Authentication at the bottom of the page.
• Save and close.

Location of the Business Central Web service URL:

Figure 88.1 Web service exposing page 42 Sales order as ODataV4 endpoint.

When the endpoint has been set up, the next step is to add an integration activity in Settings > Integration > Data Integration > New Activity.

• For the Source setting choose Type: “OData”.
• Choose the source object type (Order) from the dropdown menu.
• Click next.
• For the Target setting choose Type: “Endpoint provider”.
• Select the desired predefined Destination endpoint from the dropdown menu at “parameters”.
• Select the desired shop to export orders from.
• Select the destination API company at the bottom of the menu. This setting is for choosing the company in which the order has been placed in the case that multiple companies exist in the ERP.
• Click next.
• Check the Source checkbox to choose the target tables. Notice that there are two source tables to exposed from Dynamicweb: ObjectTypeOrder and ObjectTypeOrderLines. Make sure they each map to the corresponding target entity.
• Click finish.
• Finally, provide the activity with an optional description and click OK.

When the activity has been added, the settings menu for the activity will be visible. This menu can be accessed at any time by clicking the activity in Settings > Integration > Data Integration.

In the activity settings view the table mappings of the activity can be managed. The mappings are auto selected for all non-custom activities in Dynamicweb.

The order object type and underlying logic is more complex relative to the others. It can consume two overall entities: Sales orders and posted (invoiced) sales orders. It detects which endpoint it is automatically. No matter which entity, it is only the endpoint containing the order headers which is needed. From the header endpoint, the order object type logic automatically navigates to the underlying endpoint containing order lines.

Apart from this complexity, the order object type logic also maps entity properties in more than one table in Dynamicweb and combines multiple fields. This is visible in the mapping tables below where the Dynamicweb Destination column lists many “Handled by ObjectTypeOrder” and “Handled by ObjectTypeSalesLine”.

Mappings for ObjectTypeOrder entity:

Mappings for ObjectTypeOrderSalesLines entity:

To finish the activity setup, press save and close or save and run to perform the import job immediately.