当我寻找一个小时的空闲时间时,Microsoft Graph API上的FindMeetingTimes端点出现奇怪的行为。 我想全天参加会议。所以我的请求看起来像这样:
{
"attendees": [
{
"emailAddress": {
"address": "user@domain.com"
},
"type": "required"
}
],
"locationConstraint": null,
"timeConstraint": {
"activityDomain": "work",
"timeslots": [
{
"start": {
"dateTime": "2018-12-19T07:00:00",
"timeZone": "UTC"
},
"end": {
"dateTime": "2018-12-19T19:00:00",
"timeZone": "UTC"
}
}]
},
"meetingDuration": "PT1H",
"maxCandidates": 48,
"minimumAttendeePercentage": 100
}
我的用户在9:30 AM至11:30 AM和2:00 PM至6:00 PM可用 ,如下所示: availability 当我使用上一个主体调用API时,会得到以下结果:
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#microsoft.graph.meetingTimeSuggestionsResult",
"emptySuggestionsReason": "",
"meetingTimeSuggestions": [
{
"confidence": 100,
"organizerAvailability": "free",
"meetingTimeSlot": {
"start": {
"dateTime": "2018-12-19T11:30:00.0000000",
"timeZone": "UTC"
},
"end": {
"dateTime": "2018-12-19T12:30:00.0000000",
"timeZone": "UTC"
}
},
"attendeeAvailability": [],
"locations": []
},
{
"confidence": 100,
"organizerAvailability": "free",
"meetingTimeSlot": {
"start": {
"dateTime": "2018-12-19T12:30:00.0000000",
"timeZone": "UTC"
},
"end": {
"dateTime": "2018-12-19T13:30:00.0000000",
"timeZone": "UTC"
}
},
"attendeeAvailability": [],
"locations": []
}
]
}
从技术上讲这是正确的,但由于我的用户在12:00至1:00以及1:00至2:00都可以使用,因此不完整。
我尝试将请求分解为多个时隙,但仍然得到相同的结果。我有忘记的参数吗?
编辑:另外,如果我一天的第一次会议是从9:30到10:30,那么所有时段都将是30(10:30-11:30 ...)直到2PM({{3 }})