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
One of my applications uses MS graph to search Users / Groups in Entry ID. The search is using paging - the frontend will request the first 20 entries, and when needed, request the next 20, etc. Now, the way things are built, there's a $top parameter for User and Group, but $skip is not supported. so, if you read page 1, all is well. So, for page 2 and above, you have two options:
You specify $top = 20, and read the second page as well, returning only the results from the second page (can be done by using PageIterator). So, you'd have two requests for page 2, 3 requests for page 3, etc.
For pages > 1, instead of doing paging, you simply set $top to page * pageSize to catch everything in one request, and then return only the results in the page you actually want. (and then if you go beyond 500 you'd have to page again.. although I doubt anybody would bother to click 'fetch more results' 25 times)
So, I'm wondering - I guess there was a reason to not support $skip on User and Group. What was that reason? And what would be the recommended approach to get data for pages 2 and higher?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
One of my applications uses MS graph to search
Users
/Groups
in Entry ID. The search is using paging - the frontend will request the first 20 entries, and when needed, request the next 20, etc. Now, the way things are built, there's a $top parameter forUser
andGroup
, but $skip is not supported. so, if you read page 1, all is well. So, for page 2 and above, you have two options:PageIterator
). So, you'd have two requests for page 2, 3 requests for page 3, etc.page * pageSize
to catch everything in one request, and then return only the results in the page you actually want. (and then if you go beyond 500 you'd have to page again.. although I doubt anybody would bother to click 'fetch more results' 25 times)So, I'm wondering - I guess there was a reason to not support $skip on User and Group. What was that reason? And what would be the recommended approach to get data for pages 2 and higher?
Beta Was this translation helpful? Give feedback.
All reactions