ANVEDI File Handler
This codeunit is not available in Microsoft Dynamics 365 Business Central Online (SaaS).
This codeunit is used to sent or receive files from the local filesystem of the service tier or any UNC-network path that is accessible from the service tier.
You can select this codeunit in the communication channel and use the action Configure in the communication channel, to change the settings.
Fields
This field is part of the primary key. This field is filled automatically.
The local or network path you want to receive the files from or sent the files to.
On incoming communication channels you can filter the names of the files that should be processed. This is a Dynamics filter string and case-sensitive. To filter without checking the case, you have to add the “@” sign in front of the filter.
@*.xmlYou can specify on incoming files what the module should do with the original file
Leave it where it is. Warning: If you allow duplicate file names this will result in importing the file over and over again.
(The integer value of this option in the database is 0)
Archive the file after receiving it. The file will only be archived if it could be read. The module will archive files that cannot be processed, but are successfully retrieved (read).
(The integer value of this option in the database is 1)
Delete the file after receiving it. The file will only be deleted if it could be read. The module will delete files that cannot be processed, but are successfully retrieved (read). The data is still available from the EDI Message.
(The integer value of this option in the database is 2)
The local or network path where the archived files should be written to.
Whether a file with the same name can be retrieved by the same communication channel twice. You should only allow duplicate file names if you archive or delete the files.
A template string to build the file name. 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.