The differential query feature in AAD Graph allows for the following header:
ocp-aad-dq-include-only-delta-token: true
(Documentation: https://msdn.microsoft.com/en-us/library/azure/ad/graph/howto/azure-ad-graph-api-differential-query#AdditionalDifferentialQueryFeatures section "Differential Sync support to sync from now".)
Is there an equivalent feature (planned) for Microsoft Graph that allows me to "skip" to the end of delta stack without retrieving any data (this is the crucial part - token only)?
Not yet, but this is high on our priority list.
Related
I am querying ms graph for planner tasks https://graph.microsoft.com/v1.0/Planner/Plans/PlanID/tasks
This returns all the tasks in planner. I am hoping to filter these tasks by 'createdDateTime' greater than equals to last month. OR 'percentComplete' is less than 100.
New to querying data, so I am unsure what syntax to use. I was hoping to use $top= x would be based on createdDateTime. but if I use this
https://graph.microsoft.com/v1.0/Planner/Plans/planID/tasks?$Top=20
it still returns all of the tasks.
Thank you
Unfortunately, Planner doesn't support filters at this time. The recommended approach is for the client to read the data and filter on the client side.
For general filtering and query parameters, this documentation should help: https://learn.microsoft.com/en-us/graph/query-parameters?view=graph-rest-1.0
I'm using Groups delta API provided by Microsoft Graph API to track changes in the members of my group as follows:
https://graph.microsoft.com/v1.0/groups/delta?$select=id, mail, members&$filter=id eq '{my-group-id}'
I have been successfully able to track users' addition/deletion in my groups but recently I've come across a scenario where another group (let's call it G2) containing multiple users is a member of my main parent group (let's call it G1). Now, I've observed that the delta API won't return any change for any membership changes in G2. I was expecting that the delta API would at least return the ID of G2 to indicate that its members are changed and it needs to be re-synced.
I have also looked at transitiveMembers but it seems like this property is not supported by the delta API. Is there any way to achieve what I'm trying to do?
Thanks for any possible hints.
I user delta query to get changes to users for a particular tenant. The algorithm looks like:
Fetch all users and save delta
Use delta to get only changes
Everything works fine however the initial call to fetch all users is very slow, as I need to follow nextLink and basically if a tenant has hugh number of users ( > 1 000 000) and max number of items per page is 999 it takes a lof of the for that synchronization.
I thought, I could parallelize it - use startswith(mail,'{a}') filter and call the api for every letter in the alphabet. The problem is that with this approach I cannot fet delta link (or I would get a delta for every call).
Is there maybe a better way to speed up user fetching ?
Delta on users does not support filtering objects today on any other property than the Id. You could request support for filtering by adding an idea in UserVoice.
As a workaround you could sync the users in parallels with a filter using the GET API (/users) and then issue a delta query with $deltatoken=latest to get a token from that point and not have to sync all the changes sequentially. This doesn't guarantee consistency though.
Lastly, sync can be made faster (using delta, without parallelization) by selecting only the properties you need.
How to get resource base capacity of each day in a particular duration (Between Start & End Date) using CSOM on the project online or on-premise?
Not being able to find any solution regarding this.
I want CSOM Equivalent for the below OData Call:
/_api/ProjectData/ResourceTimephasedDataSet?$filter=ResourceId eq guid'\(resourceID)' and TimeByDay ge datetime'\(StartDate)' and TimeByDay lt datetime'\(EndDate)'
CSOM is ideally suited for getting and manipulating individual records in Sharepoint and in your case Project Web Access (PWA), but it doesn't give full access to what's available in PWA nor does it give you derived information.
There aren't CSOM equivalents for OData queries. To get this via CSOM you would need to fetch all the records the query used, apply the same joins and filtering from the query and then perform any calculations the query did.
You have an OData query to get the information you want, it would be better to use that directly.
what is the internal logic to calculate the "relevanceScore" field of people resource in Microsoft graph api ? any documentation around it publicly available ??
According to this page,
The relevance score of the email address. A relevance score is used as a sort key, in relation to the other returned results. A higher relevance score value corresponds to a more relevant result. Relevance is determined by the user’s communication and collaboration patterns and business relationships.