timeOff resource type
Namespace: microsoft.graph
Represents a unit of non-work in a schedule.
Methods
Method | Return Type | Description |
---|---|---|
List | timeOff collection | Get the list of timeOff objects in this schedule. |
Create | timeOff | Create a new timeOff object. |
Get | timeOff | Get a timeOff object by ID. |
Replace | timeOff | Replace a timeOff object. |
Delete | None | Delete a timeOff object from the schedule. |
Properties
Name | Type | Description |
---|---|---|
createdDateTime | DateTimeOffset | The time stamp at which this timeOff was first created. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z . |
draftTimeOff | timeOffItem | The draft version of this timeOff item that is viewable by managers. It must be shared before it is visible to team members. Required. |
id | String | ID of the timeOff. |
lastModifiedBy | identitySet | The identity that last updated this timeOff. |
lastModifiedDateTime | DateTimeOffset | The time stamp at which this timeOff was last updated. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z . |
sharedTimeOff | timeOffItem | The shared version of this timeOff that is viewable by both employees and managers. Updates to the sharedTimeOff property send notifications to users in the Teams client. Required. |
userId | String | ID of the user assigned to the timeOff. Required. |
JSON representation
The following JSON representation shows the resource type.
{
"createdDateTime": "String (timestamp)",
"draftTimeOff": {"@odata.type": "microsoft.graph.timeOffItem"},
"id": "String (identifier)",
"lastModifiedBy": {"@odata.type": "microsoft.graph.identitySet"},
"lastModifiedDateTime": "String (timestamp)",
"sharedTimeOff": {"@odata.type": "microsoft.graph.timeOffItem"},
"userId": "String"
}
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應