EDI Transmission Folder
This table represents a virtual folder inside of Microsoft Dynamics NAV 2017. The user can see the incoming and outgoing transmissions in this structure. You usually create one transmission folder per communication channel. But this structure can also be used to combine multiple channels and represent them in one folder.
Fields
This field is part of the primary key. You can choose any valid code.
A description shown to the end-user.
The date/time this record was modified last.
A read-only flow-field showing the total count of transmissions.
A read-only flow-field showing the count of open transmissions.
A read-only flow-field showing the count of transmissions that are in the status retry.
A read-only flow-field showing the count of successful transmissions.
A read-only flow-field showing the count of transmissions on status error.
Optional. Should not be used in combination with Business Transactions. The project code used for incoming files to find the correct mapping to convert them. On outgoing transmissions this field is used to ensure that only mappings of this project can sent files.
Optional. Should not be used in combination with Business Transactions. The format code used for incoming files to find the correct mapping to convert them. On outgoing transmissions this field is used to ensure that only mappings of this format can sent files.
Optional. Should not be used in combination with Business Transactions. The mapping code used for incoming files to find the correct mapping to convert them. On outgoing transmissions this field is used to ensure that only mappings of this code can sent files.
Whether all transmissions in this folder should be flagged as test. This does not change any logic by default. You’ll have to react to the test flag from the processing logic, if required.