In this section we describe the installation of Anveo EDI Connect for Microsoft Dynamics NAV 2017. Please follow the steps in the given order. If you want to upgrade, please see the upgrade section. You can find an installation checklist at the end of this chapter.
Importing the Objects
This section is only relevant, if you’re not using the Extension. Please change the platform to Microsoft Dynamics 365 Business Central to get the help for the Business Central Extension.
Before you are able to use Anveo EDI Connect, please import the Microsoft Dynamics NAV 2017 object files. Please go to the Object Explorer (Shift+F12) and choose “Import” from the menu bar.
You will have to import two files. We start by importing the core objects.
In this step, you should not encounter any object conflicts. The objects IDs are in a reserved range for the Anveo EDI Connect module.
Import the FOB-File for your version of Dynamics NAV. We have named the folders containing the objects accordingly to the Dynamics NAV version. In addition you can find the Dynamics NAV version in the file name.
In the next step we will import the menu suite.
There might be conflicts between our module and other modules regarding the object numbers of the menu suite. Be sure to backup your existing menu suites, before importing the Anveo EDI Connect objects.
The FOB-File containing the menu suites is called like the core objects with the suffix MenuSuite. Import the file matching your Dynamics NAV version. Please be sure to open the Import Worksheet by answering “No” to the question whether to import all objects. You will only have to import one of the provided menu suites and skip the other ones.
Remote Communication Add-In
This step is optional. You only have to install the add-in if you want to use the remote communication handler for FTP/SFTP or SMTP/POP3 based file interchange. You need to install the components on the service tier and on the development machines, where you want to be able to compile the objects.
Please start the setup program provided in the installation folder and follow the instructions. You can find the installer program in the folder Optional_Installers.
Compiling the Objects
This section is only relevant, if you’re not using the Extension.
You will now have to compile the imported objects. Please filter them in the Object Explorer by setting a filter on the Version List with the value “ANVEDI*”. Press the button “All” on the left side of the Object Explorer. Select all objects (Ctrl+A). Compile the objects (F11). If you do not need to use the remote file transfer (FTP/SMTP/POP3, …), you can ignore any errors on the following codeunits: EDI Remote Comm. Automation and EDI Remote Comm. .NET. The missing add-ins are optional. You might be able to use the components, if they are correctly installed on the service tier. To be able to compile them, they also need to be installed on the development machine. The same applies for the ZUGFeRD codeunits.
Opening the EDI Setup Window
Please restart your Microsoft Dynamics NAV 2017 client. Use the search to open the EDI Setup page.
You should now be able to see the Anveo EDI Connect menu. Open the EDI Setup window from the menu:
Departments / Administration / Application Setup / Anveo EDI / Settings / EDI Setup
If you cannot find the menu options, please check if the objects were imported correctly and if your Dynamics NAV license give you access to the Anveo EDI Connect objects. You can also try to recompile all menu suites and to restart the service tier. You can find more information in the license troubleshooting section.
Importing the License Key
Before using Anveo EDI Connect you have to set the license key. Go to the tab License in the EDI Setup window. You will find your Dynamics NAV serial number and the Dynamics NAV company name for your information. We will provide you the license based on these values. If you do not already received a license key, please send us a request including these two values. The license key should look like this: XYZZ-12GH-I89L-JJHK-KKJZ. Please enter the key in the field License Key . If the key is valid, the read only fields will be filled automatically with license details. If you license is not bound to a specific company name, you will have to enter a license company filter.
We may also provide a Partner License Key that allows you to use the customer’s license while you have your development license imported into the system. Or in other words it will check the Dynamics NAV serial number against the partner key, if the customer’s license key does not match. The key has the same format and can be entered into the field Partner License Key.
If you plan to use our module to convert EDIFACT, you will have to import the general EDIFACT data as well as the required EDIFACT versions. We describe the required steps in the next section EDIFACT Standards.