Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Office.context.mailbox.item.inReplyTo is not available on item being composed in Outlook #5239

Open
cody-lettau opened this issue Jan 4, 2025 · 1 comment
Assignees
Labels
Area: Outlook Issue related to Outlook add-ins Needs: attention 👋 Waiting on Microsoft to provide feedback

Comments

@cody-lettau
Copy link

Provide required information needed to triage your issue

The new Office.context.mailbox.item.inReplyTo property is not available on an item being composed in reply to an item or when forwarding an item.

Your Environment

  • Platform [PC desktop, Mac, iOS, Office on the web]: OWA
  • Host [Excel, Word, PowerPoint, etc.]: Outlook
  • Browser (if using Office on the web): Chrome

Expected behavior

I would expect that the parent message id value is available on this property (Office.context.mailbox.item.inReplyTo).

Current behavior

The property does not exist on the item, resulting in undefined if used. This was seen in OWA (did not test on Windows or Mac).

Steps to reproduce

  1. Click to reply to an existing message.
  2. In an on-send or compose add-in, check Office.context.mailbox.item.inReplyTo for the parent id.

Provide additional details

  1. I would like to know if this should be expected to work in an on-premise Exchange environment if the user is using a Windows Desktop client (as long as the client platform/version says it supports Mailbox 1.14 req set, even if Exchange On-prem says up to 1.5 req set only)?

Context

Add-ins need the ability to easily get the message id of the item being replied to or forwarded. Relying on Rest/Graph/EWS is not sufficient as it takes time for the item to be synced to Exchange and then it takes multiple calls to actually get the correct/usable ID (I have tried this using EWS as I have an on-prem requirement).

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

Here are some similar issues that might help you. Please check if they can solve your problem.


Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

Thanks for linking the docs, as suggested, we now check for the presence of Item in the change handler.

Reference:

Solution 2:

I believe this is the default behavior in Desktop Outlook, for which we have documented a guideline to always check for null before doing any work in the ItemChanged event handler, on this page.

Reference:

@exextoc exextoc added Needs: attention 👋 Waiting on Microsoft to provide feedback Area: Outlook Issue related to Outlook add-ins and removed Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP Similar-Issue Possible-Solution labels Jan 4, 2025
@exextoc exextoc self-assigned this Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Outlook Issue related to Outlook add-ins Needs: attention 👋 Waiting on Microsoft to provide feedback
Projects
None yet
Development

No branches or pull requests

2 participants