Skip to content

[E-Document Formats][PINT A-NZ] - Supports prefixed XML roots in PINT A-NZ import#29839

Open
GMatuleviciute wants to merge 4 commits intomicrosoft:mainfrom
GMatuleviciute:dev/aan/ubl-namespaces-issue
Open

[E-Document Formats][PINT A-NZ] - Supports prefixed XML roots in PINT A-NZ import#29839
GMatuleviciute wants to merge 4 commits intomicrosoft:mainfrom
GMatuleviciute:dev/aan/ubl-namespaces-issue

Conversation

@GMatuleviciute
Copy link

This pull request does not have a related issue as it's part of the delivery for development agreed directly with @altotovi @Groenbech96

Implementation

Enhances the PINT A-NZ E-document import process to correctly parse XML documents where the root element includes a namespace prefix (e.g., ``). Previously, the parser assumed a non-prefixed root, leading to failures with such documents.

The solution modifies the PINT A-NZ Import codeunit to:

  • Dynamically capture the full XML root path, including any namespace prefixes.
  • Utilize this dynamic root path for all subsequent XML node lookups, ensuring accurate data extraction regardless of the root element's prefix.

Adds dedicated test cases to validate the parsing of both standard and namespace-prefixed root elements, confirming the improved robustness of the import logic.

Fixes #

AndriusAndrulevicius and others added 4 commits March 10, 2026 11:54
Ensures invoice import correctly handles XML documents with namespace-prefixed root elements, improving robustness against varying XML structures.

Adds targeted tests to verify parsing of both standard and namespace-prefixed root elements, reducing risk of import failures with valid documents.
Introduces two example invoice XML documents for PINT A-NZ with and without prefixed namespaces to support testing and validation scenarios. Enables broader coverage for namespace handling in invoice processing.
@github-actions
Copy link
Contributor

Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants