Repository navigation
Access delta link from delta cmdlets #2062
Description
Customers can use the delta commands to list all changes on a resource from start to finish and the nextLink will be followed to the end as stated at Use delta query to track changes in Microsoft Graph data - Microsoft Graph | Microsoft Learn.
However, today there is no way to access the deltaLink, that's returned on the last page to track changes from "last delta call".
I want to be able to access the deltaLink as well as passing it to the delta command, so I can track the changes from the last call.
Reacted by Peter Ombwa, Martin Müller, Andrew Thompson and Simon Opelt
Activity
maisarissi commentedon Jun 2, 2023
Peter Ombwa (@peombwa) Tim (@timayabi2020) can you validate whether AutoREST supports it?
peombwa commentedon Jun 2, 2023
The CSDL will also need to be annotated to signal to SDKs that delta functions supportdeltaTokenquery parameter - microsoftgraph/msgraph-metadata#354.peombwa commentedon Jul 20, 2023
Per the discussion at microsoftgraph/msgraph-metadata#354 (comment), the SDK should instead add support
-DeltaLinkparameter, which takes the@odata.deltalinkvalue from the previous call:The implementation should ensure:
@odata.deltalinkproperty from the previous request is available to the caller. This can be a global variable, etc.Get-Mg*Delta -DeltaLinkparameter set should only support-DeltaLinkparameter to avoid sending malformed request URIs. Query parameters are specified once in the initial request. Microsoft Graph automatically encodes the specified parameter into the@odata.deltaLinkreturned in the response.pgarm commentedon Aug 30, 2023
Hey folks, just adding my 2c - been talking over this with Steve Mutungi (@SteveMutungi254) since May and then it got kinda forgotten for a while, as I mistakenly popped the bug in ADO and not here :)
Got a bit of flak from customers on this as they were building automation around the delta functionality. Given them this sample as a workaround, but certainly seems an overlooked capability ;)
Carol Kigoonya (@CarolKigoonya)
pgarm commentedon Aug 30, 2023
Copying from ADO
Solution options
Downside - only persistent within session, so not suitable for scheduled jobs (based on customer conversations, this is mostly used in non-interactive automation).
(ideally - both options to give users flexibility)
Instead of full deltaLink, can save just the deltaToken (marginally reduces memory/storage use, but makes it harder to reuse the link elsewhere.
jreinhardtproarch commentedon Nov 14, 2023
I just want to share that this is also impacting me, and is another case of the Graph SDK's lack of "fit and finish." I will attempt to use the workaround provided here, thank you, or just use Invoke-MgGraphRequest. Thanks
Jakke2440 commentedon Mar 20, 2024
any progress on this issue?
timmgreen commentedon Apr 26, 2024
How do you get the removed users with this sample? In my case it returns 380 users. The actual membership is 376 with 4 removed (1 object was deleted)
Using Get-MgGroupDelta objects that have been removed have an
@removedkey@odata.typeid@removedI don't see that when using the workaround sample. When using Invoke-MgGraphRequest and setting OutputType to PSObject that key is not included.
$groupDelta.value.'members@delta' | Get-member | select nameName
EqualsGetHashCodeGetTypeToString@odata.typeidMartinM85 commentedon Jul 8, 2024
any ETA on this issue?