You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: graph/patterns/change-tracking.md
+26-21Lines changed: 26 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ API consumers require an efficient way to acquire changes to data in the Microso
11
11
12
12
## Solution
13
13
14
-
API designers can enable the change tracking (delta) capability on a resource in the Microsoft Graph (typically on an entity collection or a parent resource) by declaring a delta function on that resource.
14
+
API designers can enable the change tracking (delta) capability on a resource in the Microsoft Graph (typically on an entity collection or a parent resource) by declaring a delta function on that resource and applying `Org.OData.Capabilities.V1.ChangeTracking` annotation.
15
15
16
16
This function returns a delta payload. A delta payload consists of a collection of annotated full or partial Microsoft Graph entities plus either a `nextLink` to further pages of original or change data that are immediately available OR a `deltaLink` to poll to get the next set of changes as they occur.
17
17
@@ -39,8 +39,8 @@ Delta payload requirements
39
39
- When an entity is deleted. the reason MUST be set to “deleted” if the entity cannot be restored.
40
40
- There is no mechanism to indicate that a resource has entered or exited the dataset based on a change that causes it to match or no longer match any `$filter` query parameter.
41
41
- When a link to an entity is deleted, when the linked entity is deleted, or when a link to an entity is added, the implementer MUST return a `property@delta` annotation.
42
-
- When a link to an entity is deleted, but the entity still exists, the reason MUST be set to `changed`.
43
-
- When a link to an entity is deleted along with the entity, the reason MUST be set to `deleted`.
42
+
- When a link to an entity is deleted, but the entity still exists, the reason MUST be set to `changed`.
43
+
- When a link to an entity is deleted along with the entity, the reason MUST be set to `deleted`.
44
44
45
45
API producers MAY choose to collate multiple changes to the same resource into a single change record.
46
46
@@ -84,10 +84,10 @@ API consumers need guaranteed data integrity over the set of changes to Microsof
Here, a user resource is updated, and there is one user added to and one removed from that user’s directReports collection. Additionally, a second user is deleted. In this case, there are no further pages of change records currently available.
125
+
Here, a user resource is updated, and there is one user added to and one removed from that user’s directReports collection. Additionally, a second user is deleted. In this case, there are no further pages of change records currently available. For detailed sequence of requests see [public documentation](https://learn.microsoft.com/en-us/graph/delta-query-users?tabs=http).
121
126
122
127
```
123
-
GET https://graph.microsoft.com/v1.0/users/delta
128
+
GET https://graph.microsoft.com/v1.0/users/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjvB7XnF_yllFsCrZJ
0 commit comments