When you implement the E-Ship/EDI functionality in your database, you get a lot of new fields added also. A lot of those fields are added in places users already interact and as such questions often come up, as to the functionality of certain fields.
The good thing is, that Lanham & Associates over the years have developed some help text, which is a good start – and it is getting better and better.
In order to get the latest On-line help, open the Shipping Setup (Shipping & Receiving –> Shipping –> Setup –> Shipping Setup.
When selecting Functions –> Online Help –> Utility Setup you may see an error:
This Error tells you that you do not have the tool installed. Unfortunately Lanham & Associates does not provide the download directly for end-users (I asked to host a copy here), so you will need to get your Partner involved. Partners should have done this at the initial implementation, but some of them tend to forget, maybe not even knowing it exist – I’ve known to forget it myself – just Say’in.
Anyways – your partner can download the LAUtil package from Lanham (I am using LAUtil1.01)
If a window open, you have the tool installed! Make sure the directory specified exists, and then go download the help files:
Downloading will take a while, so now would be a good time to get get another coke [pfsssst… Arhh]
PS – you have to say yes to the error message, if you get this one:
After the files have been downloaded you will be asked if you want to import the help file. Say YES to that – That will store the help-files inside the Navision database and will help when exporting the objects.
After the help-files have been imported, it will ask you if you want to export – Say YES to that also. This will scan you hard-drive for every directory where standard NAV help files are located, and place a copy of the E-Ship/EDI help files.
So now, in stead of getting this when asking for help
you will now get this:
Finally – you need someone to go to each workstation and to to the Shipping Setup, and do the Export only!comments powered by Disqus