What's New: Extending E-Documents with New Interface (2025 release wave 1)
The 2025 release wave 1 (version 26) of the e-document framework adds five new interfaces for building connectors. Four of them (I document sender, I document response handler, I document receiver, I received document marker) replace the old e-document integration interface. The fifth, I document action, standardizes custom document actions. The old interface is deprecated and will be removed in three waves, that is 2026 wave 2.
- Introduction and context
- Challenges in the existing framework
- Problems to solve and design goals
- Five new interfaces architecture
- Sending documents with new interfaces
- Receiving documents and new capabilities
- Key benefits and improvements
- Migration path and next steps
Overview
The video explains the technical updates for building integrations with the e-document framework in 2025 release wave 1. It covers problems in the existing framework, such as missing error handling when receiving documents and the need for “is handled” events to fetch XML, and the design goals for the new approach.
It then walks through the five new interfaces, shows how sending and receiving change, and notes that the Avalara connector was updated to use them. It ends with the migration path: the old interface is deprecated and will be removed in three waves, finishing at 2026 wave 2, and updated documentation is on Microsoft Learn.
Key points
- Sending: implement I document sender. It has the same parameters as before except for a send context codeunit as the third parameter, which wraps HTTP request and response information and any data you want to send.
- I document response handler is optional and is used for asynchronous services that process and verify contents before responding. You implement its get response method, which returns true or false.
- Receiving: I document receiver has two functions, receive documents (metadata) and download document (contents). This removes the need for the is handled event on after insert imported document.
- I received document marker is optional and acknowledges receipt to services that track received status, so they do not send the document again.
- I document action standardizes custom service calls, and the framework handles state updates so the user experience is the same across connectors.
- The framework now catches errors when HTTP communication fails on the receiving side, so it stays in control and avoids unexpected e-document states.
- The old e-document integration interface is deprecated and will be removed in three waves, that is 2026 wave 2. Migration is described as simple; follow the ‘extending the e-documents functionality’ documentation on Microsoft Learn.
Features
| Feature | Status | At | Evidence |
|---|---|---|---|
| I document sender interface | status not stated, demoed | 5:49 | |
| I document response handler interface | status not stated, demoed | 6:45 | |
| I document receiver interface | status not stated, demoed | 8:17 | |
| I received document marker interface | status not stated | 10:33 | |
| I document action interface | status not stated | 4:33 | |
| E-document framework error handling improvements | status not stated | 1:36 | |
| Send context code unit wrapper | status not stated, demoed | 6:01 | |
| Receive context data template | status not stated, demoed | 9:16 | |
| Updated Avalara connector | status not stated, demoed | 5:17 | |
| Deprecated e-document integration interface removal timeline | announced | 12:41 | “The old interfaces are deprecated and will be removed in three waves. So that is 2026 wave 2” (12:41) |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- interface “I document sender” at 5:49
- interface “I document response handler” at 6:45
- interface “I document receiver” at 8:50
- interface “I received document marker” at 10:33
- interface “I document action” at 4:33
- codeunit “send context” at 6:01
Not found in BC28-30: interface “I document sender”, interface “I document response handler”, interface “I document receiver”, interface “I received document marker”, interface “I document action”, codeunit “send context”.
Quotes
- 0:05 “the technical updates for building integrations with the e document framework that are released in uh 2025 wave 1 also known as version 26”
- 1:36 “we didn’t have any uh proper error handling when doing the receiving logic in the framework”
- 2:51 “we would like to protect against if an integration service is down, right? We want to remain in control in the framework in the”
- 3:59 “we are providing now five new interfaces and don’t worry it’s uh it is not meant to scare you that there are five because”
- 5:49 “In the new version for sending specifically you implement the I document sender and the I document sender has the same parameters as before”
- 8:17 “we had to throw in this is handled event called on after insert imported document for you to go fetch the XML from from”
- 11:27 “It is also safe because now we actually catch errors when HTTP communication fails on the receiving side.”
- 12:41 “The old interfaces are deprecated and will be removed in three waves. So that is 2026 wave 2”
- 12:53 “Migration to the new ones is simple luckily and uh you can follow the new and improved documentation we’ve made available on Microsoft learn”
- 13:23 “They are all available on AL app extensions and you can find them under e document connectors”
Disclaimers in the video
- 12:41 coming-later: old interfaces are deprecated and will be removed in three waves. So that is 2026 wave 2
Presenters (as heard): Unknown speaker.