outlook-web-addins

来源： https://stackoverflow.com/questions/63669482/how-to-get-calendarid-as-mapifolder-entryid-from-rest-api

来源： https://stackoverflow.com/questions/63669482/how-to-get-calendarid-as-mapifolder-entryid-from-rest-api

问题 I am building apps with the new technology of Office add-ins (formerly app for Office). The add-ins activate well when registered globally for the Office 365 tenant or individually by user (mechanical gear > manage add-ins). I would like my add-in to work with Office365's shared mailboxes. The add-ins do not load in Outlook desktop or in OWA when the shared mailbox is open alone. However, I managed to make it work when setting the shared mailbox as a shared folder displayed under my primary

问题 I am building apps with the new technology of Office add-ins (formerly app for Office). The add-ins activate well when registered globally for the Office 365 tenant or individually by user (mechanical gear > manage add-ins). I would like my add-in to work with Office365's shared mailboxes. The add-ins do not load in Outlook desktop or in OWA when the shared mailbox is open alone. However, I managed to make it work when setting the shared mailbox as a shared folder displayed under my primary

问题 Since shared mailbox is not supported via EWS, which we used for downloading .msg (ItemAttachments) and all other attachments were downloaded over REST We updated the outlook add-in to filter any 'ItemAttachments' and display them as un-supported for shared mailbox, which works fine. But while testing, I found that some .msg files were being downloaded via REST which was surprising and a concern. Finally got to re-create and found that: When a mail is dragged and dropped within outlook into a

问题 Our outlook add-in works in most scenarios on a shared Mailbox, except when the attachment in an email is of type " Office.MailboxEnums.AttachmentType.Item " e.g " .msg " file. Environment is Outlook web and desktop. We mostly get all attachment content via REST, as they are returned as base-64, but with " AttachmentType.Item " the body is email body and not a base-64. In this case, we make a call to EWS to download that attachment, process the body and return as byte[]; The problem we are

问题 I have notice this error happens for ALL modern Outlook Office Add-ins. Searching the net I can also see that many other Modern Outlook Add-ins are having the same issue. We know that this is an Outlook Client issue. You never get the error on OWA. I have also seen that Microsoft are suggesting Open Internet Explorer Click Tools Click Internet Options Click Security tab Select Internet Sites zone Select Enable Protected Mode (make sure box is un checked) Click OK Restart Internet Explorer and

问题 I have notice this error happens for ALL modern Outlook Office Add-ins. Searching the net I can also see that many other Modern Outlook Add-ins are having the same issue. We know that this is an Outlook Client issue. You never get the error on OWA. I have also seen that Microsoft are suggesting Open Internet Explorer Click Tools Click Internet Options Click Security tab Select Internet Sites zone Select Enable Protected Mode (make sure box is un checked) Click OK Restart Internet Explorer and

问题 We have a user for whom our pinned addin stops receiving ItemChanged event after a while (Outlook desktop only). We can always reproduce this situation in Outlook and there are no errors in the JavaScript log. What could be happening? Outlook stops firing events? Office.js loosing our event handler? How can we debug this? We can attach to the process using the Edge Dev tool. Your help would be greatly appreciated. 回答1: Thanks for reporting this issue regarding the ItemChanged Event. This is a

问题 I am developing an app for our company; because of legacy reasons when the user logs in we use a third party JSESSIONID cookie. Issue What I am seeing is that the cookie when sent to the client is not saved, and therefore not sent on subsequent requests to the server. As such, the server does not think the user is logged in. Normally I would attribute this to the blocking of 3rd party cookies feature of WebKit/View, but I have turned this off in the Safari settings. As an FYI we have an Ionic