Navision
This page is for Navision versions up to Dynamics NAV 2009 SP1.
Go to Dynamics NAV 2013 (Navision) utility page
Import tool packages
System version | Navision 6.0 SP1 |
---|---|
Tool version | 2.2 |
Tool files | |
Tool Name |
|
System version | Navision 5.0 |
---|---|
Tool version | 2.2 |
Tool files | |
Tool Name |
|
System version | Navision 4SP3 |
---|---|
Tool version | 2.2 |
Tool files | |
Tool Name |
|
System version | Navision 4SP2 |
---|---|
Tool version | 1.3 |
Tool files | |
Tool Name |
|
System version | Navision 4SP1 |
---|---|
Tool version | 1.3 |
Tool files | |
Tool Name |
|
System version | Navision 4.00 |
---|---|
Tool version | 1.2 |
Tool files | |
Tool Name |
|
Requirements and notes
- C/Front Granule 1,800
- must install C/Side client, SDK and C/Front
Import tool settings
You need to create a file called settings.xml
and place it in the same folder as the tool.
settings.xml
for Version 360 and 370b
<?xml version="1.0" encoding="utf-8"?> <Settings> <Navision> <!-- The driver to use: NDBCS Microsoft SQL Server NDBCN Navision Database Server --> <DriverType>NDBCN</DriverType> <!-- The network protocol to use for network communication, depending on the DB server SQL Server: Default Use the default Net Type. Named Pipes Use Named Pipes. TCP/IP Sockets Use TCP/IP Sockets. Multiprotocol Use Multiprotocol. Navision Database Server: netb Use NetBIOS. tcp Use TCP/IP. --> <NetType>netb</NetType> <!-- The name of the server that you want to connect to. --> <ServerName></ServerName> <!-- The database to open (see example below) --> <!-- C:\Program Files\Microsoft Business Solutions-Navision\Client\database.fdb --> <DatabaseName></DatabaseName> <CompanyName></CompanyName> <UseWindowsAuthentication>true</UseWindowsAuthentication> <!-- Login and password if windows authentication is not used --> <User></User> <Password></Password> <!-- The size of the cache in KB --> <CacheSize>2000</CacheSize> <!-- Whether or not to use CommitCache --> <UseCommitCache>false</UseCommitCache> </Navision> <!-- ERP Web Service account provided by Webmercs --> <Email></Email> <Password></Password> <!-- Email for receiving error reports. Separate multiple emails with ; --> <AdminEmail></AdminEmail> </Settings>
settings.xml
for Versions 4.0 up til 6 (Dynamics NAV 2009)
<?xml version="1.0" encoding="utf-8"?> <Settings> <Navision> <!-- The driver to use: Sql Microsoft SQL Server Native Navision Database Server --> <DriverType>Sql</DriverType> <!-- The network protocol to use for network communication, depending on the DB server SQL Server: SqlDefault Use the default Net Type. SqlNamedPipe Use Named Pipes. SqlTcpSocket Use TCP/IP Sockets. SqlMultiProtocol Use Multiprotocol. Navision Database Server: NativeNetB Use NetBIOS NativeSecureTcp Use TCPS NativeTcp Use TCP/IP --> <NetType>SqlDefault</NetType> <!-- The name of the server that you want to connect to. --> <ServerName>DB</ServerName> <!-- The database to open --> <DatabaseName></DatabaseName> <CompanyName></CompanyName> <UseWindowsAuthentication>true</UseWindowsAuthentication> <!-- Login and password if windows authentication is not used --> <User></User> <Password></Password> <!-- The size of the cache in KB --> <CacheSize>2000</CacheSize> <!-- Whether or not to use CommitCache --> <UseCommitCache>false</UseCommitCache> </Navision> <!-- ERP Web Service account provided by Webmercs --> <Email></Email> <Password></Password> <!-- Email for receiving error reports. Separate multiple emails with ; --> <AdminEmail></AdminEmail> </Settings>
How to use the import tool
Overview
For each order, the general version of the import tool does the following:
- Check if all the products exist in the accounting system. If any products don't exist, it will attempt to create them.
- Check if the customer exists. If the customer does not exist, it will attempt to create a new customer (unless we are instructed not to do so).
- Create salesorder
- Create purchase order (please see notes). Requires that ERP# field is filled out in webshop admin/catalog/vendors.
The ERP# is the ID of the vendor in your accounting system - the link between the vendor in the webshop and the vendor in your system.
Installing the tool
- download and unpack the files in a folder of your choice
- create a file called
settings.xml
according to the instructions and place in the same folder - check requirements and notes section and the info on how to run the tool
The following general requirements apply
- The computer on which you run the tool must have internet access
- The computer on which you run the tool must have access to the accounting system
- In most cases the computer on which you run the tool must have the accounting system client installed
- Windows XP/2003 operating system with .Net Framework 2.0 or higher
Running the tool
The tool would normally be run using Windows Scheduler at intervals that suit your needs (once a day, once every hour, etc). It can also be run from the command line.
<Tool name> -batch|-get|-transform|-import [o:<orderId>] [fd:<dd/MM/yyyy>] [td:<dd/MM/yyyy>] [l:<days>] [p]
required: one of the following
-batch | run complete import cycle (i.e. |
---|---|
-get | download order XML |
-transform | convert order XML based on rules for given accounting system |
-import | import transformed/converted orders |
optional: any number of the following
o:<orderId> | choose specific order |
---|---|
fd:<date> | choose orders after specified date |
td:<date> | choose orders before specified date |
l:<days> | choose all orders from <days> days ago until today |
p | choose "printed" orders |
<Tool name> refers to the name of the exe-program in the tool package (such as wmx2navision.exe).
<Tool name> -batch
This is the most common way to run the tool. It will download and import all orders with status ordered or shipped, set the webshop order to imported and write the accounting system order number in webshop order detail upon successful import of the order into the accounting system. If an error occurs during the import (say, an incorrect/unknown customer number), an email is sent to the AdminEmails indicated in settings.xml.
example: c:\>wmx2navision.exe -batch
<Tool name> -batch o:<orderNumber>
Same as above, except that it will only download one specific order. Use this when you test the tool.
example: c:\>wmx2navision.exe -batch o:26999
If you know what you are doing, then you can use any of the options described above. If you are unsure whether you should use any of the options, then you probably shouldn't.
Troubleshooting
When you run the tool it creates a report file in a sub-folder called \LOG - one file each time. If there are errors, or you have questions about a specific order import, we need to you send us that file. Every parameter that is set during the import process is logged, and in case of serious errors it will contain general error messages.