/
Uniconta

Uniconta

By Artyom Sherstobitov
May 27, 2019

Import tool package

System version

Unknown

Tool version

1.0

Tool files


Tool name

wmx2uniconta.exe

Uniconta is a web-based solution, we can run this tool on our servers.

Requirements and notes

(warning) You need to create a file called settings.xml and place it in the same folder as the tool.
(info) You can define own log4net configuration — just place log4net.config in the same folder as the tool.

settings.xml

<?xml version="1.0" encoding="utf-8"?>
<Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <Account>
        <!--Uniconta account provided by Uniconta-->
		<AccessIdent>GUID VALUE</AccessIdent>
		<Login>XXX</Login>
		<Password>YYY</Password>
    </Account>
    <!-- ERP Web Service account provided by Webmercs -->
    <Email></Email>
    <Password></Password>
    <!-- Email for receiving error reports. Separate multiple emails with ; -->
    <AdminEmail></AdminEmail>
</Settings>

ERP WebService can not be accessed from the FTP machine using default HTTPS scheme .
To fix it, the following line should be added to the Settings.xml:

<WebServiceUrl>http://secure.webmercs.com/erplinkservice/service.asmx</WebServiceUrl>

How to use the import tool

Overview

For each order, the general version of the import tool does the following:

  1. Check if all the products exist in the accounting system. If any products don't exist, it will attempt to create them.
  2. 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).
  3. Create salesorder
  4. Create purchase order (please see notes). Requires that ERP# field is filled out in webshop admin/catalog/vendors.

(info) 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, transform, import)

-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

 

(warning) 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.


Related content