microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
The list of participants in Teams meeting can only be retrieved up to 100 people.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
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.
2. Graph API communications/calls/{id}/participants
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):
- 1. Notification by the Microsoft.Graph.Communications.Calls library
- Microsoft Graph .NET Client Library(Microsoft.Graph.Communications.Calls) Version 1.2.0.4161
- 2.communications/calls/{id}/participants
- Microsoft Graph JavaScript Client Library(@microsoft/microsoft-graph-client) Version 3.0.2
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing communications/calls/{id}/participants with the Microsoft Graph JavaScript client and reviewing the attached partitipants_result_json.txt. Check the reported behavior with more than 100 participants and with $top below 100. Done means determining whether pagination is supported or whether the limitation needs to be documented or escalated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100