Default new E-Document services to import v2 and let users select the draft format#9702
Merged
Conversation
…ersion on service card Make Version 2.0 (draft pipeline) the default import process for newly created E-Document services via InitValue on field 31, and surface the "Import Process" version selector on the E-Document Service card so users can view and switch versions. Existing services are unaffected. No v1 deprecation/obsoletion: local format apps are not yet migrated off the v1 inbound path, so v1 remains fully functional and selectable. Test preservation: pin all nine LibraryEDocument service factories to Version 1.0 so the existing receive/flow/E2E suites (which rely on the v1 mock subscribers) keep exercising v1 exactly as before. Add a unit test asserting a freshly initialized service defaults to Version 2.0. Update module docs to note the new default and selectability. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The ForNAV connector creates its E-Document Service via Insert() without setting "Import Process". Now that the field defaults to "Version 2.0", the service inherited the v2 draft pipeline, which broke the SubmitGetDocuments integration test (codeunit 148221) that asserts the v1 inbound behavior of creating a Purchase Invoice E-Document directly. ForNAV inbound is not migrated to the v2 pipeline, so explicitly pin the service to "Version 1.0" at creation time, matching the pattern already used for the mock services in codeunit "Library - E-Document". Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PR #9654 makes the "Import Process" selector visible and defaults new services to Version 2.0, but the V2 import pipeline also needs to know how to read an incoming structured e-document into a draft. That format is the service-level "Read into Draft Impl." field (field 33): for already-structured formats such as PEPPOL XML the structuring step returns Unspecified, so the read step falls back to this field. When it is left Unspecified, "E-Doc. Unspecified Impl." runs and import fails with "No method to read the e-document has been provided." That field was not on the page, so a user who selected V2 had no way to choose the format. This adds it to the Purchase Draft group (visible for Version 2.0) as "Draft Format", with a tooltip, updates the module docs, and adds a page test verifying the format is selectable and persisted. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 57f500b9-871d-4cf4-bdc1-751bea22d091
4 tasks
darjoo
approved these changes
Jul 24, 2026
gggdttt
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
New E-Document services should default to the v2 import pipeline and let users actually configure it end-to-end. This needs two things that belong together:
That format is the service-level
"Read into Draft Impl."field (table 6103, field 33). For already-structured formats such as PEPPOL XML the "Structure received data" step returnsUnspecified, soImportEDocumentProcess.ReadIntoDraftfalls back to this service field:If the service field is also
Unspecified,E-Doc. Unspecified Impl.runs and import fails with "No method to read the e-document has been provided." Defaulting to v2 without exposing this field would leave users unable to make v2 work.What
Import Process= Version 2.0 (InitValue) and removeVisible = falseon the selector."Read into Draft Impl."to the Purchase Draft group on the service card (shown only for Version 2.0), captioned Draft Format, with a tooltip covering PEPPOL vs. auto-resolved PDF/ADI.AB#580191