Office.js item saveAsync doesn't save all fields on new appointment

Question

I am using Office.context.mailbox.item.saveAsync in an Outlook add-in to save a new appointment. The returned item id is used to fetch the appointment using the REST api (a get request to Office.context.mailbox.restUrl + '/v2.0/me/events/' + itemId). This returns an appointment where Start, End, and Organizer is set correctly, but the Subject, Body, Location, Recurrence, Attendees is not set.

Does saveAsync not save all fields on the appointment?

I am using the REST api because the Recurrence field is not available through the Office.context.mailbox.item in older versions of the Outlook JavaScript API.

What client are you on? Outlook Web Access or Outlook Windows Desktop, or Mac Outlook etc. If on Windows Desktop, and in Cached Mode, it is likely those properties haven't sync'ed up to the server yet. The Recurrence Field was added to help avoid these sync issues, so that should be used when possible. — user7823505
– user7823505, Commented Nov 28, 2018 at 20:42

user7823505 · Accepted Answer · 2018-12-18 22:45:31Z

0

This scenario occurs when calling Office.context.mailbox.item.saveAsync on a new Calendar item that has not been sent yet. This has been fixed in the new Outlook Web beta. The API should behave as designed in Mail and on Existing Calendar items. Note that for existing Calendar items, an update may be sent out to attendees depending on the changes that the user or the add-in made in the compose form.

answered Dec 18, 2018 at 22:45

user7823505

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Office.js item saveAsync doesn't save all fields on new appointment

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related