Developer Workstation Installation

Open 'Developer Workstation Installation' wizard, choose your scenario to see more provider-related information of the installation manual.

Interfaces Add-on Installation

Installation of Interfaces Add-on for Sana Commerce is the same for SDK and the 'Ready to deploy' version. In order to install Interfaces Add-on for Sana Commerce follow these steps:

Step 1: Copy the 'Sana.Commerce.Tasks.Interfaces.dll' file from the 'bin' folder of the Interfaces add-on package to the 'bin' folder of the Sana Commerce backoffice.

Step 2: Execute the 'CreateStoredProcedures.sql' script, from the 'scripts' folder, on your database. It will create the stored procedures that are needed for the correct work of the 'Product Import', 'Order Export' and 'Product Stock and Price Import' tasks.

Step 3: Configure the 'Product Import', 'Order Export', 'Product Stock and Price Import' and 'Order Line Import' tasks. This configuration is performed in the backoffice 'web.config' file:

  • Locate the 'Interfaces configuration section.txt' file, which contains the tasks configuration sections;
  • Copy the whole text of this file into the <tasks> section of the 'web.config' file, so it will look as follows:

    Make sure to paste the contents of the 'Interfaces configuration section.txt' file just at the end of the <tasks> section and do not delete the existing tasks.
<tasks taskContentConnectionStringName="LocalSqlServer">
<task name="ProductImport"
title="Product import"
type="Sana.Commerce.Tasks.Import.ProductImportTask, Sana.Commerce.Tasks.Interfaces"
  sourceCustomerProviderId = "NavisionFashionCustomerProvider"
  sourceCatalogProviderId = "NavisionFashionCatalogProvider"
  destinationWebsiteCode = "B2xSql"
  sourceWebsiteCode = "B2xNav2009Standard"
<task name="OrderExport"
  title="Order export"
  type="Sana.Commerce.Tasks.OrderExport.OrderExport, Sana.Commerce.Tasks.Interfaces"
  sourceWebsiteCode = "B2xSql"
  destinationOrderProviderId = "NavisionStandardOrderProvider"
  destinationCustomerProviderId = "NavisionStandardCustomerProvider"
<task name="ProductStockandPriceImportTask"
  type="Sana.Commerce.Tasks.ProductStockandPriceImport.ProductStockandPriceImportTask, Sana.Commerce.Tasks.Interfaces"
title="Product stock and price import" 
  sourceCatalogProviderId = "Navision2009StandardCatalogProvider"
  destinationWebsiteCode = "B2xSql"
  sourceWebsiteCode = "B2xNav2009Standard"
<task name="OrderLineImport"
  title="Order lines import"
  type="Sana.Commerce.Tasks.OrderLineImport.OrderLineImportTask, Sana.Commerce.Tasks.Interfaces"
  sourceOrderProviderId = "Navision2009StandardOrderProvider"
  destinationWebsiteCode = "B2xSql"     
  • Check the configuration nodes and specify the necessary values.

For more information about the tasks configuration please read the 'Add-ons and Modules' section.

Step 4: Add 'Sana.Commerce.Tasks.Interfaces' assembly mapping to the <hibernate-configuration> section in the 'web.config' file:

<hibernate-configuration xmlns="urn:nhibernate-configuration-2.2">
                  <mapping assembly="Sana.Commerce.Tasks.Interfaces" />

Microsoft Dynamics NAV Configuration

Configure Microsoft Dynamics NAV for the 'Product Import', 'Order Export', 'Product Stock and Price Import' and 'Order Line Import' tasks:

Step 1: Open the Microsoft Dynamics NAV client, select 'Webshop' in the left pane and open 'Webshop Card'.

Step 2: In the 'Online Shipment' section you need to specify the type of the sales line representing the 'Shipping Cost' with its object identifier and the same for the 'Payment Cost' in the 'Online Payment' section. For more information please read this chapter.

Step 3: Specify Template Customer No. that will be used during the 'Product Import' and 'Product Stock and Price Import'. The product prices imported to the Commerce Provider webshop will be based on the specific prices for this customer. The same goes for the stock amount of the products which will be based on the warehouse configured for this customer.

The 'Prices Including VAT' option on the customer card must be enabled, since the Commerce Provider webshop, where the products will be imported in, only supports the B2C scenario.