Creating a job mapping
What is a job mapping? That is an NAV type mapping that is run by the job queue in order to process certain records in a table. The goal is to regularly check the table if there are (new) records that need to be processed, i.e. exported in most cases.
Depending on the data table that you want to process, this mapping contains a table loop over this table with appropriate filters that preselect records. For example it filters out all records that have already been processed by other NAV mappings and are already exported. You should have a field in the table that you can use for your filter, e.g. a boolean field named “Transferred to EDI”. It is set to “TRUE” for all records that have already been exported and you can filter it to “FALSE” to identify the records that need to be exported.
Another condition for allowing the processing could be the amount of a posted sales invoice: if the amount is zero, it shall not be exported.
If you have additional conditions that need to be fulfilled, apply these filters as well. In order to start the further processing, you need to set up the post processing on this table to pass the records to the actual NAV mapping which transfers the data to the buffer tables (and sets the boolean mentioned above to “TRUE”), followed by the export mapping that writes the file to a folder etc.
A big advantage of this method is that every post processing is a separate transaction and even if one processing failes for some reason, it won’t stop the whole export process and the other records will still be exported.