- More flexibility around the format of the data
- Defaults to fill in gaps and derive data appropriately
- Automation to the point where you need not lift a finger
- Accountability – TransPost records everything
MYOB Import produces a log file, ‘MYOBPLOG.TXT’ if you use Classic Premier or Enterprise or ‘importlog.txt’ if you use AccountRight Live. This does contain a list of what was not imported with error codes but not the data imported. If you do not conscientiously move or rename it before the next import it will be overwritten. What can you do when you import a couple of files and then realise that there was a problem with the first import?
TransPost records everything
- Daily TransPost Log file recording events, errors and warnings
- Imported data file, recording imported data
- Unprocessed data, so it can easily be reprocessed
- Error log
Daily Transpost Log
The dailyTransPost Log file covers all activity. A new one is created each day. It records:
- What file is being imported and where to
- Warnings for invalid data ignored
- Messages passed back from MYOB
- Error messages when a transaction fails
- Success of an import
While it is preparing data for input, retrieving the necessary data for each transaction, TransPost verifies that the data is valid and logs both errors which will prevent TransPost from even attempting to import the data, such as invalid Item Numbers, and warns when less essential items are invalid, for example Job Numbers.
Every line in a sale is validated, and its errors reported, with line numbers, before the sale is accepted or rejected. This is useful when preparing and importing transactions with large numbers of item lines.
This log is displayed on the Import tab within TransPost, as it happens, so you can see immediately if the process is not working.
For each file imported an Imported Data file is created. This will contain the ID number (e.g. invoice or bill number) assigned to each transaction imported together with the data values supplied so you have an exact record of what happened.
Developers note: If the log field used in the mapping is a primary key in your data source then this file provides a cross reference between that key and the corresponding invoice number, purchase number or other transaction ID within AccountRight.
TransPost also records what did not get imported. If a transaction fails its data is copied exactly to the unprocessed data output for the batch. Also if an import is cancelled part way through, for example if there is a communications error or the run is just cancelled, the reminder of the data is copied.
This provides exactly the data that needs to be reprocessed when you have resolved to problem. Just run the Unprocessed Data file through the same mapping.
Many of our users have automated the entire process. When it is working well nobody really looks at the daily log. One of our users complained that on the rare occasion there was a problem, after weeks of working perfectly, it was easy to overlook.
To address this issue, we recently introduced the Error Log. It contains errors, and only errors, from the daily log files. If nothing failed it does not even get created so its appearance is a signal that something failed. Once the error has been resolved, this file can be removed or renamed and you can relax and continue to let the data flow into AccountRight until it reappears. All being well that will not be very often.