问题描述
在使用 Microsoft Graph Explorer 时，我注意到当您提交像 https 这样的组增量请求时://graph.microsoft.com/beta/groups/delta，您将收到提供@odata.nextLink 的回复.但是，当我遵循提供的链接时，我开始获得与先前响应中完全相同的组集，如果我继续遵循链接，则会使用另一个 @odata.nextLink 导致无限递归.预期的行为是在某个时间点获得 @odata.deltaLink 但在收到的响应中永远不会到达.我的 Azure 环境中有 63 个组.
While working with Microsoft Graph Explorer, I noticed that when you submit a groups delta request like https://graph.microsoft.com/beta/groups/delta, you will get a response with the @odata.nextLink available. However, when I follow the provided link, I start getting exactly the same set of groups as in the previous response with another @odata.nextLink leading to the endless recursion if I keep following the links. The expected behavior is to get @odata.deltaLink at some point but in never arrives in the responses received. I have 63 groups in my Azure environment.
尝试从查询中排除成员，但发送 https://graph.microsoft.com/v1.0/groups/delta?$select=displayName.在这种情况下，我在关注 @odada.nextLink 一次后在第二页上得到了 @odata.deltaLink.
Tried excluding members from the query but sending https://graph.microsoft.com/v1.0/groups/delta?$select=displayName. In this case, I get @odata.deltaLink on the second page after following @odada.nextLink once.
推荐答案
好的，我想出了如何解决这个问题.当 Delta 更改返回具有超过 1000 个成员的组时，将返回相同的数据集但添加其余成员.这似乎是一个无限循环，但实际上正在带来其他成员.那么如果你在不扩展成员的情况下使用 select 进行查询，那么你就避免了无限循环.
ok , i figured it out how to solve the issue. When Delta changes returns groups that has more than 1000 members , then is returning the same data set but adding the rest of members. It seems that is an inifinite loop but really is bringing the rest of members. Then if you do a query with select without expanding members, then you avoids the infinite loop.
https://docs.microsoft.com/en-us/graph/delta-query-groups#paging-through-members-in-a-large-group
这篇关于Microsoft Graph API Groups Delta Query Never Returns Delta Query(使用 nextLink 的无限循环)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！