MS-Graph 事件中的组织者和 isOrganizer 属性是否有效? [英] Are the organizer and isOrganizer Attributes in MS-Graph event working?

问题描述

我正在尝试使用 MS Graph API 与技术用户代表资源创建新事件.事件已创建，但响应中不考虑或忽略组织者和 isOrganizer 属性.

I'm trying to use the MS Graph API to create a new event with a technical user on behalf of a resource. The event is created, but the organizer and isOrganizer Attributes are not considered or ignored in the response.

我尝试了多个请求以及v1.0"和beta"模式.在这个 SO 问题 如何创建当前用户不是使用 Microsoft Graph API 的组织者的事件 据说这在原始帖子(2016 年)发布时尚未实现.但是我在 Graph-API 文档中没有找到任何内容，说这行不通.

I tried multiple requests as well as in 'v1.0' and 'beta' mode. In this SO question How to create event where current user not organizer using Microsoft Graph API it is stated that this is not implemented at the time of the original post (2016). But I didn't find anything in the Graph-API docs, saying that this would not work.

这是请求正文:

{
                "subject": "Instant Meeting: " + user_name,
                "body": {
                    "contentType": "HTML",
                    "content": "Dieser Termin wurde vom Konferenzraum eingestellt"
                },
                "isOrganizer": "false",
                "organizer" : {
                    "emailAddress": {
                        "address":user_email,
                        "name": user_name
                    }
                }, 
                "start": {
                    "dateTime": start,
                    "timeZone": "Europe/Berlin"
                },
                "end": {
                    "dateTime": end,
                    "timeZone": "Europe/Berlin"
                },
                "location":{
                    "displayName": room.get('name'),
                    "locationEmailAddress": room.get('email'),
                    "locationType" : "conferenceRoom"
                },
                "attendees": [
                    {
                    "emailAddress": {
                        "address":user_email,
                        "name": user_name
                        },
                    "type": "required"
                    },
                    {
                    "emailAddress": {
                        "address":room.get('email'),
                        "name": room.get('name')
                        },
                    "type": "resource"
                    }
                ]
                }

响应的相关部分是:

response.get('organizer')

{'emailAddress': {'address': 'testraum-nichtbuche...t-mail.de', 'name': 'TestRaum - NICHT BUCHEN'}}
'emailAddress': {'address': 'testraum-nichtbuche...t-mail.de', 'name': 'TestRaum - NICHT BUCHEN'}
__len__: 1

response.get('isOrganizer')

True

如果这工作正常，我希望组织者"是 user_email 并且标志被设置为 False.

If this worked properly, I would expect the 'organizer' to be user_email and the flag to be set to False.

谁能为此提供一个工作示例?

Can anyone provide a working example for this?

谢谢！

推荐答案

这种行为没有改变.organizer 和 isOrganizer 属性不能由调用者定义，它们由 Exchange 自动分配:

This behavior has not changed. The organizer and isOrganizer properties cannot be defined by the caller, they are automatically assigned by Exchange:

• 使用 Outlook 日历 REST API 设置活动组织者

Outlook Calendar Rest API(使用/me/events 请求创建会议并更改组织者)

outlook.com rest api 不正确的组织者电子邮件

如何使用 Microsoft Graph API 创建当前用户不是组织者的事件

这篇关于MS-Graph 事件中的组织者和 isOrganizer 属性是否有效?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！