4.8.0

Description

The focus for this release has been the new recovery function to ease the handling of recurring errors. There have also been improvements to the handling of sending attachments so we can send incoming documents from non-posted documents. We have also worked on performance optimizations to provide some speed-ups of message generation. This is of course not all but it covers the biggest things we think are important.

Recovery Function

A new tool called the recovery function has been added in this release. This utility function allows you to configure automatic retries of specific types of errors. For instance, if you get locks when processing messages you can configure the recovery function to automatically retry the message X amount of times.

You can use regex or sub-string matching to filter the errors you want to have the automatic retries kick in. The amount of times to retry a specific error is also configurable so you have full flexibility configuring the system.

When a message is under retry it will state so in the column "Message Text", it will also indicate in that text on how many times left it will retry the failure until it considers it a loss. The actual error message will be printed in "Internal Error Text" so you can act on it, if necessary.

Configuration

The settings page is where you configure which types of errors should be retried and how many times they should be retried. This can be configured on a per-message-code and per-profile basis so different combinations can be retried a different amount of times despite being the same type of error.

You also have the option to use regex which enables fine-grained control on matching the specific error message. Don't go too crazy though! It can be hard to understand if you go full regex.

Skipped Lines

We have elected to hide "skipped lines" by default when viewing contents of messages. Skipped lines are lines that are generated but ignored by both our Cloud Integration Platform and internal processing of messages. You can remove the filter quite easily if you want to see these lines, they can sometimes contain useful information such as filters.

Limit Messages

We've added a limit to how many messages we process at one time when the job queue runs. The limit is currently set to 100 but may change in the future depending on need. The reason for adding this limit is to avoid blocking customers job queues for too long. Since only two job queues can run at the same time in Business Central Online across all companies in a tenant we do not want our job to be the reason other might not run.

Changelog

• Recovery functions has been implemented to automatically reset certain types of errors.

• Allow incoming documents to be sent on documents other than posted documents.

• Remove orphan lines in the GEDI Message Lines table in deletion job.

• Fix the cleaning routine for posted and up-auto finished messages to not leave orphan lines.

• Limit number of messages to process in one run, the limit is now 100 messages.

• Buffer message lines in memory before writing to table in batches.

• Added functions to "modify if possible" to tolerate errors when running modify.

• Disable editing of entry number in message queue.

• Improve handling of modify errors in control to avoid blowing up the job queue.

• Hide skipped lines by default when viewing message lines.