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.location object not recognized correctly #453

Closed
rodrigoguariento opened this issue Apr 1, 2019 · 1 comment

Comments

@rodrigoguariento
Copy link

rodrigoguariento commented Apr 1, 2019

Dears,

When we use the following code, the room created in Admin Office 365 is not treated like a "resource room":

Office.context.mailbox.item.location.setAsync('Mezanino');

The outcome is an unknown place, without Exchange tracing. Namely, when we add the same resource manually using Outlook Web or Microsoft Office Oultook, selecting the same room, the room is treated like a sort of object which permits Exchange book that time and location, and show it on its room scheduling.

Is it a bug?

How we can add a Office.context.mailbox.item.location as an object, like does Outlook Web and Microsoft Outlook?! Actually the setAsync is seemly treating the information like a simple text without references.

The only way that I found to solve this is add the 'Mezanino' room as an attendee too, beyond the location. But do it is a jerry-rig.

ex1

Using https://developer.microsoft.com/en-us/graph/graph-explorer# we can see:

ex2

@exextoc
Copy link
Collaborator

exextoc commented Apr 10, 2019

This is by design. Unfortunately, item.location does not currently support multiple locations. This has been resolved with a new Enhanced Location API that supports multiple locations. Keep in mind the API is currently in preview and may be prone to issues. Enhanced Location API is available in the Preview API Requirement Set. You could also either use the work around like you suggested or use REST to set the locations as well.

@dmahugh dmahugh closed this as completed Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants