Add vendor matching telemetry to E-Document import#8711
Open
ventselartur wants to merge 2 commits into
Open
Conversation
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
When an E-Document is imported and a purchase draft is prepared, the vendor is resolved through several strategies (by number, GLN, VAT id, service participant, name and address) and can also be carried over from history or assigned by a provider. Today we only emit a single boolean telemetry point indicating whether a vendor was found, which makes it impossible to understand how vendors are being matched in the field, where matching falls back to fuzzy name/address logic, or why no vendor was assigned. This change enriches the import session telemetry so we can analyze vendor-matching behavior and diagnose failures.
AB#639684
Summary
Vendor Match Methodtelemetry inE-Document Import Helper.FindVendor, tagging which identifier (No,GLN,VAT Id) matched the vendor.Vendor Matched By Name Not Addressboolean telemetry when a name-only candidate is found during fuzzy matching.Vendor Assignment Sourcetelemetry inEDoc Prepare Purch. DraftdistinguishingAlready Assigned,Provider,History, andNone.Vendor Info Presentboolean andVendor Match Methodoutcomes (None - No Vendor Info,Service Participant,Name and Address,None - No Match) inE-Doc. Providers.