Office.js issue with fetching “to” field of a message in Outlook for Mac 16.18 (181014)
up vote
0
down vote
favorite
I’m working on an add-in for Microsoft Outlook, and I’ve noticed that in the latest version of Outlook for Mac, 16.18 (181014), our add-in is unable to retrieve recipients of a draft that’s just been created. Our add-in is attempting to fetch the recipients using office.js’s Office.context.mailbox.item.to.getAsync() method. To reproduce this issue:
- While reading an email in your inbox, click the “reply” button to begin drafting a new email; the new draft should automatically have a recipient in the “to” field because it is a reply.
- From this draft, open an add-in which will try to fetch the draft’s “to” recipients by calling
Office.context.mailbox.item.to.getAsync(). No recipients will be found. - In the “to” field of the draft, add an additional recipient, and
then remove this recipient. - Try to fetch the recipient from your
add-in again by callingOffice.context.mailbox.item.to.getAsync()-
this time you will be given the “to” recipients correctly.
We’ve only noticed this issue in version 16.18 (181014). It appears that the user must manually edit the “to” field before the getAsync() method is able to give us its contents.
outlook-addin office-js outlook-web-addins outlook-for-mac
asked Nov 9 at 19:51
Steve M
112
add a comment |
up vote
0
down vote
favorite
I’m working on an add-in for Microsoft Outlook, and I’ve noticed that in the latest version of Outlook for Mac, 16.18 (181014), our add-in is unable to retrieve recipients of a draft that’s just been created. Our add-in is attempting to fetch the recipients using office.js’s Office.context.mailbox.item.to.getAsync() method. To reproduce this issue:
- While reading an email in your inbox, click the “reply” button to begin drafting a new email; the new draft should automatically have a recipient in the “to” field because it is a reply.
- From this draft, open an add-in which will try to fetch the draft’s “to” recipients by calling
Office.context.mailbox.item.to.getAsync(). No recipients will be found. - In the “to” field of the draft, add an additional recipient, and
then remove this recipient. - Try to fetch the recipient from your
add-in again by callingOffice.context.mailbox.item.to.getAsync()-
this time you will be given the “to” recipients correctly.
We’ve only noticed this issue in version 16.18 (181014). It appears that the user must manually edit the “to” field before the getAsync() method is able to give us its contents.
outlook-addin office-js outlook-web-addins outlook-for-mac
asked Nov 9 at 19:51
Steve M
112
Curious if you tried saving the message first using Office.context.mailbox.item.saveAsync to see if it allows you to get the "to" field after that.
– Brian Clink
Nov 9 at 21:45
I've been testing this with thesaveAsync()call, and it turns out that this is not fixing the issue for us in Outlook for Mac; it also has made it so that we cannot detect recipients in Outlook 2016 for Windows and the Outlook Web App. Could there be an issue with the way Outlook for Mac returns the recipients array to us with theitem.to.getAsync()method?
– Steve M
Nov 14 at 0:45
This issue has been fixed, request you to please update to the latest Insider build.
– Mac_Outlook_Extensibility
Nov 14 at 10:37
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I’m working on an add-in for Microsoft Outlook, and I’ve noticed that in the latest version of Outlook for Mac, 16.18 (181014), our add-in is unable to retrieve recipients of a draft that’s just been created. Our add-in is attempting to fetch the recipients using office.js’s Office.context.mailbox.item.to.getAsync() method. To reproduce this issue:
- While reading an email in your inbox, click the “reply” button to begin drafting a new email; the new draft should automatically have a recipient in the “to” field because it is a reply.
- From this draft, open an add-in which will try to fetch the draft’s “to” recipients by calling
Office.context.mailbox.item.to.getAsync(). No recipients will be found. - In the “to” field of the draft, add an additional recipient, and
then remove this recipient. - Try to fetch the recipient from your
add-in again by callingOffice.context.mailbox.item.to.getAsync()-
this time you will be given the “to” recipients correctly.
We’ve only noticed this issue in version 16.18 (181014). It appears that the user must manually edit the “to” field before the getAsync() method is able to give us its contents.
outlook-addin office-js outlook-web-addins outlook-for-mac
asked Nov 9 at 19:51
Steve M
112
I’m working on an add-in for Microsoft Outlook, and I’ve noticed that in the latest version of Outlook for Mac, 16.18 (181014), our add-in is unable to retrieve recipients of a draft that’s just been created. Our add-in is attempting to fetch the recipients using office.js’s Office.context.mailbox.item.to.getAsync() method. To reproduce this issue:
- While reading an email in your inbox, click the “reply” button to begin drafting a new email; the new draft should automatically have a recipient in the “to” field because it is a reply.
- From this draft, open an add-in which will try to fetch the draft’s “to” recipients by calling
Office.context.mailbox.item.to.getAsync(). No recipients will be found. - In the “to” field of the draft, add an additional recipient, and
then remove this recipient. - Try to fetch the recipient from your
add-in again by callingOffice.context.mailbox.item.to.getAsync()-
this time you will be given the “to” recipients correctly.
We’ve only noticed this issue in version 16.18 (181014). It appears that the user must manually edit the “to” field before the getAsync() method is able to give us its contents.
outlook-addin office-js outlook-web-addins outlook-for-mac
outlook-addin office-js outlook-web-addins outlook-for-mac
asked Nov 9 at 19:51
Steve M
112
asked Nov 9 at 19:51
Steve M
112
asked Nov 9 at 19:51
Steve M
112
asked Nov 9 at 19:51
Steve M
112
asked Nov 9 at 19:51
Steve M
112
112
Curious if you tried saving the message first using Office.context.mailbox.item.saveAsync to see if it allows you to get the "to" field after that.
– Brian Clink
Nov 9 at 21:45
I've been testing this with thesaveAsync()call, and it turns out that this is not fixing the issue for us in Outlook for Mac; it also has made it so that we cannot detect recipients in Outlook 2016 for Windows and the Outlook Web App. Could there be an issue with the way Outlook for Mac returns the recipients array to us with theitem.to.getAsync()method?
– Steve M
Nov 14 at 0:45
This issue has been fixed, request you to please update to the latest Insider build.
– Mac_Outlook_Extensibility
Nov 14 at 10:37
add a comment |
Curious if you tried saving the message first using Office.context.mailbox.item.saveAsync to see if it allows you to get the "to" field after that.
– Brian Clink
Nov 9 at 21:45
I've been testing this with thesaveAsync()call, and it turns out that this is not fixing the issue for us in Outlook for Mac; it also has made it so that we cannot detect recipients in Outlook 2016 for Windows and the Outlook Web App. Could there be an issue with the way Outlook for Mac returns the recipients array to us with theitem.to.getAsync()method?
– Steve M
Nov 14 at 0:45
This issue has been fixed, request you to please update to the latest Insider build.
– Mac_Outlook_Extensibility
Nov 14 at 10:37
Curious if you tried saving the message first using Office.context.mailbox.item.saveAsync to see if it allows you to get the "to" field after that.
– Brian Clink
Nov 9 at 21:45
Curious if you tried saving the message first using Office.context.mailbox.item.saveAsync to see if it allows you to get the "to" field after that.
– Brian Clink
Nov 9 at 21:45
I've been testing this with the
saveAsync() call, and it turns out that this is not fixing the issue for us in Outlook for Mac; it also has made it so that we cannot detect recipients in Outlook 2016 for Windows and the Outlook Web App. Could there be an issue with the way Outlook for Mac returns the recipients array to us with the item.to.getAsync() method?– Steve M
Nov 14 at 0:45
I've been testing this with the
saveAsync() call, and it turns out that this is not fixing the issue for us in Outlook for Mac; it also has made it so that we cannot detect recipients in Outlook 2016 for Windows and the Outlook Web App. Could there be an issue with the way Outlook for Mac returns the recipients array to us with the item.to.getAsync() method?– Steve M
Nov 14 at 0:45
This issue has been fixed, request you to please update to the latest Insider build.
– Mac_Outlook_Extensibility
Nov 14 at 10:37
This issue has been fixed, request you to please update to the latest Insider build.
– Mac_Outlook_Extensibility
Nov 14 at 10:37
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53232428%2foffice-js-issue-with-fetching-to-field-of-a-message-in-outlook-for-mac-16-18%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53232428%2foffice-js-issue-with-fetching-to-field-of-a-message-in-outlook-for-mac-16-18%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Curious if you tried saving the message first using Office.context.mailbox.item.saveAsync to see if it allows you to get the "to" field after that.
– Brian Clink
Nov 9 at 21:45
I've been testing this with the
saveAsync()call, and it turns out that this is not fixing the issue for us in Outlook for Mac; it also has made it so that we cannot detect recipients in Outlook 2016 for Windows and the Outlook Web App. Could there be an issue with the way Outlook for Mac returns the recipients array to us with theitem.to.getAsync()method?– Steve M
Nov 14 at 0:45
This issue has been fixed, request you to please update to the latest Insider build.
– Mac_Outlook_Extensibility
Nov 14 at 10:37