Did you get a chance to try this? if this doesn’t work, you can make this change,
#set($nextLink = $response[“@odata”]?.nextLink) #if($nextLink)
$log.info(“Next Link: $nextLink”)
$endpoint.fullUrl = $nextLink #else
$log.error(“Next Link is null or not found in the response.”)
TERMINATE #end
As per the experience i have, working with GRAPH API, when we reach the last page, in that case odata.nextLink property will be completely missing from the response. So can you please try below snippet of the code and see if that helps
I have not tried it yet in ISC but just extending the VLT logic mentioned above by other colleagues. Please check and let us know if this helps. Otherwise, please try with @colin’s suggestion.
The standard connector doesn’t let you manage all the attributes which SailPoint support confirmed and hence having to implement a webservice connector instead.
does $log.info() actually work in the paging? would that dump to ccg.log or somewhere else? i’m trying to use this and it doesn’t appear to be working.