Developer Workstation Installation

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

Import NAV Objects

Now the code base and the SQL database are in place and the Microsoft Dynamics NAV administration is configured to be accessed, the NAV side can be configured. 
To install the Sana Commerce objects in the Microsoft Dynamics NAV administration the following steps are required:
  • Backup standard NAV objects;
  • Import new objects. These are new custom SC objects which most likely do not yet exist in the administration;
  • Update changed NAV objects. Some standard NAV objects are changed for SC that need to be updated.
Backup Standard NAV Objects:

The Sana Commerce installation includes the custom NAV objects as well as the standard objects modified for SC. In order to have the possibility to uninstall correctly the Sana Commerce solution in future, you must backup the objects changed for SC and keep this backup because it will be needed during the uninstallation of SC. It is required to do the backup of the SC objects before starting to import them. For more details on the uninstallation procedure please follow this link.

Take the following steps in order to create the backup:

Step 1: Open the 'Changed Objects Overview' chapter of the online help and locate the list of the standard NAV objects changed by SC.

Step 2: Open the Object Designer in the Microsoft Dynamics NAV Client and select the objects which are listed in the aforementioned chapter. Export the selected objects to a 'fob' or 'txt' file.

Step 3: Place the resulting 'fob' or 'txt' file to a reliable backup location and keep it for the whole period of using Sana Commerce.

Import New NAV Objects

Step 1: Locate the NAV objects:

The objects for Microsoft Dynamics NAV 5 Standard or PFS are delivered on demand.

The following files are placed for import in each localization folder:
SC_objects (.fob and .txt). These files contain new Sana Commerce objects.
SC_Standard_objects (.fob and .txt). These files contain changed standard NAV objects.
The objects for Microsoft Dynamics NAV 5 with Pebblestone Fashion add-on are also delivered on demand. If you use Microsoft Dynamics NAV with Pebblestone Fashion add-on, you should request the 'Pfs Fashion Add-on' package.

If you update the SC installation to a new version or the NAV objects from your current database have been customized, you should, in order to save your changes, manually update the new NAV objects from the SC project. To do this, you should export the changed NAV objects to a text file, then, using a merge tool, you merge this file with the 'SC_objects.txt' file and import the newly merged text file into Microsoft Dynamics NAV.

Some input text fields used within the Sana Commerce webshop have a different maximum length in Microsoft Dynamics NAV 4 and 5. For now, Microsoft Dynamics NAV 5 field length validation is used in SC by default. Therefore, if you use Microsoft Dynamics NAV 5 there is no need to change input text field validation. But if you use Microsoft Dynamics NAV 4, change to the validation for the select input text fields in order to prevent validation errors. Read the chapter 'Configure field lengths for NAV 4' for more details.

Step 2: Open the Microsoft Dynamics NAV client, go to 'Tools' in the main menu and select 'Object Designer'.

Step 3: Go to 'File' and select 'Import'. Locate the file 'SC_objects.fob' in the 'Navision' folder of the Sana Commerce release package and press 'OK'. The following pop-up window appears: 

Importing of New NAV Objects 

Step 4: Press 'Yes' to start the import of the new objects. An overview of the import is shown when it is finished:

Importing of New Objects is Finished 

The Sana Commerce menus will only be shown after the import if the SC ID range is added to the Microsoft Dynamics NAV (developer) license used in the administration. 
Update Changed NAV Objects 
Updating of changed NAV objects can be done in two ways:
  • If the standard NAV objects in your database have already been customized, you should manually merge these objects with the objects from the SC package. Resulted objects will contain both your customization and SC changes:

Step 1: Export the changed NAV objects to a text file using 'Object Designer'.

Step 2: Merge the text file with the 'SC_Standard_objects.txt' file using a merge tool. Check the 'Microsoft Dynamics NAV Changes' section for an overview of the changes to the standard NAV objects.

Step 3: Import the resulting text file in Microsoft Dynamics NAV.

Step 4: Click 'All' in 'Object Designer'.

Step 5: Apply filter on the 'Compiled' column (click 'View > Field Filter' or press 'F7') and enter 'No' in the filter field:

Applying Filter on the 'Compiled' Column

Step 6: Select all uncompiled objects and click 'Tools > Compile' (or press 'F11'):

Preparing to Compile the Objects

  • If standard objects in your Microsoft Dynamics NAV database are without any customization you can use the 'Import Worksheet' window:

Step 1: Open 'Object Designer'.

Step 2: Go to 'File' and select 'Import'. Locate the file 'SC_Standard_objects.fob' and press 'OK'.
You will get the following pop-up message:

Conflicts Between Standard and Imported Objects were Found

Step 3: Click 'OK' to open the 'Import Worksheet' window:

The 'Import Worksheet' Window

A list of changed objects is shown. Make sure to select 'Replace' for changed objects in your administration to guarantee that the SC changes are correctly imported.

Objects were Imported Successfully