ANVEDI Remote Comm. Handler
For new implementations, please check if you can use the File Exchange Service. The components described in this chapter will not be supported on new Microsoft Dynamics NAV 2017 (BC22 and above) releases. We will only provide updates in case of security vulnerabilities.
This codeunit is not available in Microsoft Dynamics 365 Business Central Online (SaaS). This codeunit requires the installation of external .NET components, which are provided free of charge.
This codeunit is used to sent or receive files from/to a remote server. This codeunit requires the installation of additional .NET components on the service tier. (Or on each machine in the case of the Classic Client of NAV). Please see the Installation chapter for more details.
You can select this codeunit in the communication channel and use the action Configure in the communication channel, to change the settings.
TLS versions: All of our on-premise components are using the .NET framework and support the TLS versions that are currently supported by your operating system an .NET 3.5
Fields
This field is part of the primary key. This field is filled automatically.
A description of the server / settings.
The protocol to be used. Depending on the direction of the communication channel you can only select some of the protocols.
For outgoing transmissions only. Use SMTP to send e-mail like messages.
(The integer value of this option in the database is 0)
The SMTP part of the module is intended for use with technical systems and not for creating human-readable emails.
For incoming transmissions only. Retrieve data from a POP3 server.
(The integer value of this option in the database is 1)
Use FTP oder FTP over SSL.
(The integer value of this option in the database is 2)
Use SFTP (SSH).
(The integer value of this option in the database is 3)
The server name / DNS address or IP.
The port that should be used. Most protocols have default ports defined, if you set this value to 0.
The user name that should be used to contact the server.
The password that should be used to authenticate the user to the server.
The encryption mode. Select SSL for FTPS or to use encrypted SMTP or POP3.
Do not use encryption or use the default encryption in case of SFTP.
(The integer value of this option in the database is 0)
This option was named SSL before version 5.2. We renamed the option because not all protocols use SSL for encryption.
Use encryption.
(The integer value of this option in the database is 1)
Only used by SMTP: The sender e-mail address.
Only used by SMTP: The sender name in clear text.
Only used by SMTP: The recipient if the receiver identification is empty.
Only used by SMTP: The subject of the message. You can also use all variables that are available for the field Filename Template.
SMTP only: Whether to sent the data as body or as an attachment.
SMTP only: When data is sent as an attachment you can define a static text that is sent as the body of the message. This field is not directly available in the user interface. We do not support variables inside the text part.
The SMTP part of the module is intended for use with technical systems and not for creating human-readable emails.
The action that should be executed after importing the transmission. This aqction is executed after the data was successful retrieved and stored. It is also executed if the data cannot be converted, as the data is available to Microsoft Dynamics NAV 2017 for re-processing.
No action after import.
(The integer value of this option in the database is 0)
Archive the data after import (not supported by all protocols).
(The integer value of this option in the database is 1)
Delete the data after import.
(The integer value of this option in the database is 2)
Whether the same file name can be imported multiple times by the same communication channel.
The cross-reference type that should be used to set the sender partner from the sender identification.
Available in module version 4.00 and above.
The cross-reference type that should be used to set the receiver partner from the receiver identification.
Available in module version 4.00 and above.
Whether to keep the network connection open when retrieving or sending more than one transmission.
Only used for FTP and FTPs. The data transfer mode to be used.
Select automatically,.
(The integer value of this option in the database is 0)
Passive mode. Select implementation automatically.
(The integer value of this option in the database is 1)
Active mode. Select implementation automatically. This will require that the active FTP ports on the machine running the code is directly available from the internet.
(The integer value of this option in the database is 2)
Extended port mode
(The integer value of this option in the database is 3)
Extended passive mode
(The integer value of this option in the database is 4)
Traditional passive mode
(The integer value of this option in the database is 5)
Extended passive mode
(The integer value of this option in the database is 6)
Active port mode
(The integer value of this option in the database is 7)
When to start the encryption for FTPs connections.
Default behaviour.
(The integer value of this option in the database is 0)
Start the encryption on connection to the server.
(The integer value of this option in the database is 1)
Connect unencrypted and change to encryption afterwards.
(The integer value of this option in the database is 2)
You can select the FTP data mode. Depending on the content of the data the text mode will change the encoding of the file during transfer and sometimes the representation of line breaks.
The data is considered to be binary. This is required, for example, for PDF files.
(The integer value of this option in the database is 0)
The data only contains text and can be re-encoded.
(The integer value of this option in the database is 1)
A template string to build the file name for outgoing files. You can use any constant text that is valid inside file names. We support several global variables that can be used inside the filename. Because the module does not know the content of the file and the used buffer structures you cannot directly access data from the file.
The following variables are available:
The entry number of the transmission. Can be used to generate a unique filename.
{Reference}
Not supported in older versions. Output the reference number (document number) that is stored with the transmission. If business transactions are used it is automatically set.
The description of the transmission.
Deprecated. Alias for {Sender Partner}.
The sender partner code.
The sender partner identification.
Deprecated. Alias for {Receiver Partner}.
The receiver partner code.
The receiver partner identification.
The project of the mapping that has generated the data.
The format of the mapping that has generated the data.
The code of the mapping that has generated the data.
The year with century information, e.g. 2019.
The year, e.g. 19.
The month as two digits.
The day as two digits.
The calendar week, represented as two digits.
The quarter, represented as two digits.
The hour of the transmission creation.
The minutes of the transmission creation.
The seconds of the transmission creation.
It is possible to create custom variables via the callback functionality of the module, if you need, for example, to include a document number in the filename.
Currently not supported.
The directory on the server, if the protocol support remote directories.
Used for SFTP only. Stores the private key. Anveo EDI Connect does not officially support the use of private keys. You can try it with an OpenSSH formatted key, but our support cannot help you with key errors. The module currently has no option to remove the key, once it is set. You either have to create a new communication channel, or empty the BLOB by using the Microsoft Dynamics NAV 2017 development environment.
Currently not used.
Optional: The fingerprint of the remote SFTP server to compare after connecting. If the keys do not match an error is generated. If you leave the field empty the module will accept any certificate for the server.
Whether the SSL certificate has to be valid or whether all certificates are accepted.
Ignoring SSL error will make man in the middle attacks possible. You should try to resolve the SSL error instead of accepting any remote certificate.
If you set the internal and external encoding, the module will try to re-encode the data. You should set these fields to empty, if you are not sure whether a re-encode is required. This way the data is not changed on sending/receiving by the component.
If you set the internal and external encoding, the module will try to re-encode the data. You should set these fields to empty, if you are not sure whether a re-encode is required. This way the data is not changed on sending/receiving by the component.