search

OfficeDev / office-js

A repo and NPM package for Office.js, corresponding to a copy of what gets published to the official "evergreen" Office.js CDN, at https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
https://learn.microsoft.com/javascript/api/overview
Other
663 stars 94 forks source link

Office.context.mailbox.item.getConversationIndexAsync() and Office.context.mailbox.item.getItemClassAsync() failing for new Outlook client #4664

Open teejay001 opened 1 month ago

teejay001 commented 1 month ago

Provide required information needed to triage your issue

Your Environment

Expected behavior

The conversationIndex should be returned correctly from the call.

Current behavior

Office.context.mailbox.item.getConversationIndexAsync() fails with an error message below image

Steps to reproduce

  1. Ensuring you are referencing the latest requirement set for outlook (1.14, https://learn.microsoft.com/en-us/javascript/api/requirement-sets/outlook/requirement-set-1.14/outlook-requirement-set-1.14?view=common-js-preview)
  2. Make a call to get the conversationIndex as described n the document
  3. conversationIndex is returned on all Windows client except the new Office Client

Link to live example(s)

  1. https://learn.microsoft.com/en-us/javascript/api/outlook/office.messagecompose?view=outlook-js-1.14&preserve-view=true#outlook-office-messagecompose-getconversationindexasync-member(1)

Provide additional details

  1. The new outlook client being used is of the version below image

Context

We cannot deploy as it is, business requirement is to know the conversationIndex reference for further processing.

Useful logs

image

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.

teejay001 commented 1 month ago

Since both endpoint were introduced at the same time, perhaps it's the same issue affecting both. Office.context.mailbox.item.getItemClassAsync() also fails with the same error on new outlook client

rkpathak commented 1 month ago

Thanks for reporting this issue. It has been put on our backlog. We unfortunately have no timelines to share at this point

Internal tracking id: Office: [290513]