Release 26.5.59 on 17.11.2026
· 4 min read
This release makes processing more robust after interruptions: steps that stay Started after a lost session or a service restart are now set to Failed by a new job queue cleanup and can be repeated with the new Force Repeat action, and repeating a Cegedim sending step checks the existing Cegedim job instead of sending the document a second time. Incoming eDocuments show an editable Purchase Document Type, extensions can supply the SEPA direct-debit mandate (BT-89/BT-91), deleting an eDocument also deletes its addresses, and the UNECE units and payment means lists are downloaded from a new address.
Feature
- Incoming eDocuments have a new column Purchase Document Type (Invoice / Cr.Memo) on the process card and on the eDocument card. It shows the type read from the xInvoice type code (BT-3) and can be changed until the purchase document is created: a manual choice rewrites the xInvoice type code to
380(invoice) or381(credit memo), so Create invoice creates the chosen purchase document. Once the purchase document exists, the field is no longer editable. See Purchase Document Type of Incoming eDocuments (INC-1663)
Bugfix
- Repeating a Cegedim SEND step called
DocumentSendagain unconditionally, so a step that failed after the send (for example on the status poll or a session abort) sent the document to Cegedim a second time. The Cegedim job is now stored in the new eDocument field Cegedim Job Guid right after the send. On a repeat, the status of that job is checked first: Failed → the document is sent again (logged), still in progress → the existing job is polled, finished → done. Get Cegedim Status on the eDocument card uses the same job. For eDocuments sent before this release, the existing Cegedim Guid is used when it holds a job. If Cegedim no longer knows a stored job (purged or test account), the repeat ends with the error from the status call (CHN-588) - A step whose session or service died while it ran stayed Started, and the eDocument stayed Step started for good, because Repeat only takes failed steps. Steps now record Started At, Session ID and Server Instance ID. The new job queue codeunit 5563632 mseBC mseDoc365 Stuck Steps sets a started step to Failed (with an error entry) when its task is no longer scheduled, its session is no longer active and it was started more than the wait time ago (default 60 minutes, Parameter String = minutes). It never restarts a step itself. The new action Force Repeat on the eDocument card repeats a started step directly; it is refused while the step may still be running and asks for confirmation for sending steps (SEND, DVELOP-SEND) because of a possible second send. The cleanup only runs once a job queue entry is set up — use its own job queue category, not the mseDoc365 category. Steps stuck before this release have no start time and are not changed by the cleanup. See Interrupted Steps (CHN-589)
- The step Applying sending target failed with Target Entry selection was not unique although the target list had a single entry for the customer. Deleting an eDocument left its addresses behind, so a new eDocument with the same number (for example after a number series reset) inherited them, and an address without recipient made the target lookup count the whole list. Deleting an eDocument now also deletes its addresses, copying an address keeps its recipient (Origin Type/Origin No.) when the source has none, and an address without recipient on a list with several entries now stops with a clear error naming the eDocument and the target list. Leftover addresses from earlier deletions are not cleaned up automatically (CHN-579)
Enhancements
- New integration event
OnBeforeResolveDirectDebitMandateon the buffer table mseBC mseDoc365 S. Inv.Buffer for payment means59(SEPA direct debit). An extension that keeps its mandates outside the BC table SEPA Direct Debit Mandate (for example a payment add-on with its own mandate management) can supply the mandate ID (BT-89) and the debtor IBAN (BT-91) for the posted invoice or credit memo; the document number is passed to the event. A handled mandate without IBAN stops with a clear error. The creditor ID (BT-90) is still taken from the company bank account. See Direct Debit Mandates from Extensions (INC-1663)
Changes
- Download UNECE Units List on mseDoc365 Units and Download on mseDoc365 Payment Means now load their lists from
https://statics.mse365-services.net/mseDoc365/, because the previous addresswebservice.mse-addons.deno longer delivers them (HTTP 401). The ZUGFeRD definition behind the Setup field Webservice URL is unchanged