[Bug]: CC Recipients are not stored for retrieved emails
Nobody has claimed this yet.
- Dominant language
- AL
- Stars
- 683
- Forks
- 459
- Avg merge
- 3d 26m
- Merged PRs (30d)
- 633
Description
Describe the issue
When retrieving emails with the Outlook/Graph integration, the to recipeint and cc recipients are requested by the APIClient but they are never stored. This way, when using the reply all functionality afterwards, it is unclear who gets the reply.
Expected behavior
When retrieving emails, corresponding recipients are stored so they can be retrieved when necessary.
Steps to reproduce
- In Business Central, using a feature that processes inbound email via the Outlook/Graph integration (e.g. an AI agent such as the Sales Order Agent or Payables Agent), have an external sender send an email that is also sent to a CC recipient.
- Let Business Central pick up and process the incoming email through the normal inbound flow.
- Observe that there is no way to retrieve the To and CC recipients.
- Enable diagnostic/trace logging (or debug) around the attachment-fetching logic in the Outlook API helper codeunit, and confirm that the to and cc recipients are in the select statement in the API client.
Additional context
No response
I will provide a fix for a bug
- I will provide a fix for a bug
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the Outlook API helper codeunit from the attachment-fetching logic mentioned in the issue, and inspect how the API client's selected To and CC recipients move through the inbound email flow. Confirm where retrieved email data is stored and how reply-all reads it. Done means both recipient sets are available after retrieval for reply-all use.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100