Removed instances are represented by their id and an object. These annotations use the format The annotations are included in the response of the initial delta query request. Relationships on users and groups are represented as annotations on the standard resource representation. Updated instances are represented by their id with at least the properties that have been updated, but additional properties may be included. Newly created instances of a supported resource are represented in the delta query response using their standard representation. Resource representation in the delta query response For example, the following request returns changes for the groups matching the IDs specified in the query filter. Scoping filters allow you to track changes to one or more specific users or groups by object ID. Selecting those properties allows tracking of changes to user's manager and group memberships. $select also supports manager and members navigation properties for users and groups respectively. If a change occurs to a property that is not selected, the resource for which that property changed does not appear in the delta response after a subsequent request. If a $select query parameter is used, the parameter indicates that the client prefers to only track changes on the properties or relationships specified in the $select statement. The number of objects in each page can vary depending on the resource type and the type of changes made to the resource.įor the message resource, see details for query parameters support in a delta query.įor the user and group resources, there are restrictions on using some query parameters: Assume that the same item can show up anywhere in the sequence and handle that in your merge logic. Note the general limited support of the following optional query parameters:ĭo not assume a specific sequence of the responses returned from a delta query. Microsoft Graph adds the specified parameters automatically for all subsequent requests. The calling application only needs to specify the query parameters once upfront. Microsoft Graph automatically encodes the specified parameter into the or provided in the response. If a client uses a query parameter, it must be specified in the initial request. When carrying out delta query, you can copy and apply the or URL to the next delta function call without having to inspect the contents of the URL, including its state token. Therefore, it's not required to repeat them in subsequent delta query requests. The state tokens also encode and include other query parameters (such as $select) specified in the initial delta query request. The following details are what you need to know about them:Įach token reflects the state and represents a snapshot of the resource in that round of change tracking. The URL includes a $skipToken, and a URL includes a $deltaToken. State tokensĪ delta query GET response always includes a URL specified in a or response header. Updates made before the initial request are summarized on the resource returned as its latest state. Resources that have been created and deleted prior to the initial delta query won't be returned. The initial request to the delta query function (no $deltaToken or $skipToken) will return the resources that currently exist in the collection. Microsoft Graph returns a response describing changes to the resource since the previous request, and either a URL or a URL. This request may be made immediately after completing step 2 or when the application checks for changes. When the application needs to learn about changes to the resource, it makes a new request using the URL received in step 2. For future requests, the application uses the URL to learn about changes to the resource. If a URL is returned, there is no more data about the existing state of the resource to be returned. The application continues making requests using the URL to retrieve all pages of data until a URL is returned in the response.ī. If a URL is returned, there may be additional pages of data to be retrieved in the session. Microsoft Graph sends a response containing the requested resource and a state token.Ī. The application begins by calling a GET request with the delta function on the desired resource. Tutorial: Use Change Notifications and Track Changes with Microsoft Graph Use delta query to track changes in a resource collection
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |