Skip to main content

Release 26.5.47 on 15.07.2026

· 2 min read

This release adds an optional duplicate-check step to inbound purchase-invoice processing, lets the inbound document type be forced from the processing job, resets a sales document's last export date when it is posted, and extends the extension's public API surface with a new sending-target error event, public record-reference and validation helpers, an Azure blob upload helper and paginated blob listing.

Feature​
  • Inbound purchase-invoice processing can now block re-importing a document that already exists. A new optional processing step CHECK_DUPLICATE, placed after FIND_VENDOR in a process template, checks the unposted Purchase Header (Document Type = Invoice) and the posted Purch. Inv. Header for the same vendor and the same vendor invoice number (the Exchanged Document ID carried in the xRechnung) and raises a hard error on a match. The step is opt-in per template — it is not added to the default templates — and is skipped when the external number is empty (CHN-332)
  • The inbound document type can now be forced from the processing job's "Document Type" field, so a job can pin the type it produces regardless of detection. New DocumentTypeCode overloads thread the value through eDoc creation and process management
  • A sales document's last export date is now reset when the document is posted, so a document that is exported, posted and posted again is picked up for a fresh export instead of being treated as already sent
Enhancements​
  • New extensibility event OnBeforeThrowErrorWhileApplySendingTarget on the management codeunit, raised before the "no sending target" error at both sites where it can occur, allowing an extension to supply an alternative sending target and suppress the error
  • The public API surface has been widened for consuming extensions: the record-reference AddTable and GetFieldValue helpers and the ValidateInvoice overloads are now public, a new AzureStorage.AddBlob() upload helper is available, and Azure blob listing now paginates beyond 5000 entries using the response continuation marker (NextMarker)