Navision2013
Navision / Microsoft Dynamics NAV 2013
System version | Dynamics NAV 2013 + |
---|---|
Tool version | 2.0.9 |
Tool files | |
Tool Name | wmx2navision2013.exe |
Requirements and notes
- Page Web Services must be set up on the server side
- list of pages to set up as web services
- MSDN guideline to set up Page web services
List of required values should be filled and sent to support@webmercs.com:
Field
Value
Example
Gen_Bus_Posting_Group
INDLAND
VAT_Bus_Posting_Group
INDLAND
Customer_Posting_Group
UDLAND
Unit_Of_Measure
STK
Inventory_Posting_Group
HANDEL
Gen_Prod_Posting_Group
PRODUC
VAT_Prod_Posting_Group
MOMS25
Import tool settings
You need to create a file called settings.xml
and place it in the same folder as the tool.
<?xml version="1.0" encoding="utf-8"?> <Settings> <WebServices> <!-- General URL to Dynamics NAV Web Services in the form http://<Server>:<WebServicePort>/<ServerInstance>/WS/<CompanyName>/services --> <Url></Url> <!-- Username and password for accessing Dynamics NAV web services. Leave empty to use current windows user account --> <Username></Username> <Password></Password> <!-- Custom value of web service timeout in seconds --> <TimeoutSec>200</TimeoutSec> </WebServices> <!-- ERP Web Service account provided by Webmercs --> <Email></Email> <Password></Password> <!-- Email for receiving error reports. Separate multiple emails with ; --> <AdminEmail></AdminEmail> <!-- If you want to test without writing order# to webshop database or marking the order as exported --> <TestMode>true</TestMode> </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.