OData provider

The OData Provider is a purpose-built provider. It must be paired with an Endpoint Provider. Currently the only officially supported OData endpoints originate from Dynamics 365 Business Central (D365BC).

The OData Provider uses a set of object types. These object types contain predefined mappings between specific entities in D365BC and specific tables in Dynamicweb. There is an object type called Custom. Use this when a source endpoint is custom or does not have a matching object type. When object type Custom is used, then OData Provider delegates to Dynamicweb Provider which in turn can expose all Dynamicweb tables.

A how-to guide on using the OData - and endpoint providers to set up data integration between Dynamicweb and Microsoft Business Central can be found here.

The OData provider as source for a data integration activity is intented for exporting Dynamicweb data to Dynamics 365 Business Central. 

The OData provider supports export of the following object types:

  • Order
  • User
  • User Address
  • User Customer
  • User Customer Ship-to Address

Using the OData provider as destination provider is intented for importing data from Business Central to Dynamicweb.

There are two use cases of the OData provider as destination: OData API imports and OData V4 imports. The latter has the upside of utilizing predefined mappings for all object types where as the API use case will essentially delegate to the Dynamicweb provider to allow the user to define custom entity mappings.

Country  Maps between countries in D365BC and countries in Dynamicweb.
Currency

Maps between currencies in D365BC and currencies in Dynamicweb.

Requires a match between base currency (LCY) in D365BC and default currency in Dynamicweb. Without a match all exchange rates will be wrong.

Custom Contains no predefined mappings. This object type will allow a Dynamicweb user to map from any OData entity to any Dynamicweb table and from OData property to Dynamicweb table column. This is achieved by delegating to Dynamicweb Provider.
Manufacturer Maps between vendor cards in D365BC and manufacturers in Dynamicweb.
Order Contains predefined mappings for two entities. It maps between sales orders in D365BC and orders in Dynamicweb and it maps between posted sales orders (sales invoices) in D365BC and orders in Dynamicweb.
Product group Maps between item categories in D365BC and groups in Dynamicweb.
Product translation Maps between item and variant translations in D365BC and product translations in Dynamicweb.
Product unit translation  Maps between unit of measures translations in D365BC and product unit translations in Dynamicweb.
Product unit  Maps between units of measures in D365BC and product units in Dynamicweb.
Product variant

Maps between item variants in D365BC and variants in Dynamicweb.

Variants will only be added to Dynamicweb if master item is already known. Product in Dynamicweb will be converted to a product family master with underlying variants.

Product Maps between item cards in D365BC and products in Dynamicweb. Base unit of measure and vendor relations are also mapped.
Product-unit relation Maps one-to-many relation between item and its unit of measures in D365BC and product stock matrix in Dynamicweb.
User

Maps between B2B contacts in D365BC and B2B users in Dynamicweb.

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

User address Maps between B2B contact’s alternative addresses in D365BC and the B2B users’ address lists in Dynamicweb.
User customer

Maps between B2B customers in D365BC and B2B users in Dynamicweb.

Each customer 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.

 
User customer ship-to address Maps between B2B customer ship-to addresses in D365BC and B2B user’s address lists in Dynamicweb. Both the customer-based user accounts and contact-based user accounts will get ship-to addresses.
Sales person

Maps between sales people in D365BC and users in Dynamicweb.

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.

Stock amount Maps inventory amount per item per variant per unit of measure per location in D365BC to product stock matrix in Dynamicweb.
Stock location Maps locations in D365BC to stock locations in Dynamicweb.