#10022 Known senders table should only be inserted to when the task is coming from an email
The Known Senders table now only gets populated when tasks arrive from email, preventing unwanted entries when tasks are created by manually uploading PDFs.
- 1files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-08-08 by mynjj · 1 file (+2 -0), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Restricts population of the PA Known Sender table to email-sourced tasks only
- Prevents table entries when tasks are created through manual PDF uploads
- Uses the same source-distinguishing approach as GetAgentTaskMessagePageId
- Fixes issue where table was incorrectly populated for non-email task creation
- Behaviour changes for users or extensions.
AL objects touched
- Table 3308 “PA Known Sender”, PayablesAgent: modified
Context
- Work items: AB#646072
- Labels: AL: Apps (W1), Team: Finance
- Systems: development
- From the description: “The table was getting populated when creating tasks by manually uploading a PDF. This functionality is scoped to tasks received by email.”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).