Config / Data Exchange / ANVEDI Email Communication

ANVEDI Email Communication

Requires Anveo EDI Connect version 5.0.0.17 and Microsoft Dynamics Business Central V19 or newer.

This codeunit allows you to send EDI messages as emails using the Dynamics build-in emailfunctionality. You have to configure the email setup of Dynamics first. You can try to select the codeunit in the communication channel by entering the Codeunit ID 5327389.

Configuration

The basic configuration like the server and sender is done in the Dynamics email account setup. In the communication channel you can assign the communication channel to an email scenario. The scenario can be assigned to a specific email account. This way you can use multiple accounts and sender adresses. The module provides two email scenarios “EDI Data” and “EDI Notification”, but you can use any scneario from the system or any extension (including your own).

Fields

Communication Channel Code

This field is part of the primary key. This field is filled automatically.

Description

A description of the server / settings.

Email Scenario

Select the email scneario from Dynamics. The scneario is used to find the email account for sending data.

Fallback Recipient

If no email recipient is found during the creation of the message the fallback from this field is used.

Subject

The subject, you can use the same placeholders as for the filename template.

Send File as Attachment

Whether to sent the data as body or as an attachment.

Filename Template

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:

{Entry No.}

The entry number of the transmission. Can be used to generate a unique filename.

{Description}

The description of the transmission.

{Sender Party}

Deprecated. Alias for {Sender Partner}.

{Sender Partner}

The sender partner code.

{Sender Identification}

The sender partner identification.

{Receiver Party}

Deprecated. Alias for {Receiver Partner}.

{Receiver Partner}

The receiver partner code.

{Receiver Identification}

The receiver partner identification.

{Project}

The project of the mapping that has generated the data.

{Format}

The format of the mapping that has generated the data.

{Code}

The code of the mapping that has generated the data.

{CCYY}

The year with century information, e.g. 2019.

{YY}

The year, e.g. 19.

{MM}

The month as two digits.

{DD}

The day as two digits.

{WW}

The calendar week, represented as two digits.

{QQ}

The quarter, represented as two digits.

{HH}

The hour of the transmission creation.

{mm}

The minutes of the transmission creation.

{ss}

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.