Open yabe-yoshito opened 1 year ago
That sounds like a problem we could be running into as well. We still need to plan our investigation. I will get back to you :)
We've conducted testing and don't run into this issue. At least not with 100+ application participants in the meeting. Not too sure what would happen with unique users in the meeting, but given that the identity isn't really of concern in the participant collection, but rather the participant object itself, I don't think there should be any issues.
Describe the issue I'm using the following means to retrieve information on Teams meeting participants, but if there are more than 100 participants, we can only retrieve data up to 100 participants as a list of participants. 1.Notification by the Microsoft.Graph.Communications.Calls library.
Is there any way to get a list of participants (over 100) in a Teams meeting?
Code Snippet This is the result of retrieving the list of participants in a meeting with more than 100 participants by "Notification by the Microsoft.Graph.Communications.Calls library ; only up to 100 participants are displayed, and there is no @odata.nextLink property. partitipants_result_json.txt
Expected behavior Information on the 100th participant and beyond can be retrieved, or a link to the list of the 100th participant and beyond can be obtained with the @odata.nextLink property.
Graph SDK (please complete the following information):
Logs API call is successful. See Code Snippet for results
Additional context I verified that the @odata.nextLink property is obtained by specifying $top to a value less than 100 in the API for communications/calls/{id}/participants, but the result did not change. I think it could be a bug in the API.