microsoftgraph / microsoftgraph/msgraph-sdk-java
Error in PATCH onlineMeeting
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Java
- Sterne
- 444
- Forks
- 154
- Ø Merge
- 18 Std. 28 Min.
- Gemergte PRs (30 T.)
- 4
Beschreibung
Describe the bug
Hello,
I have integrated microsoft graph sdk to programmatically manage onlineMeetings. Since a couple of days I am getting errors in updating onlineMeetings (PATCH methods) even with this simple request:
PATCH https://graph.microsoft.com/v1.0/users/<owners_uid>/onlineMeetings/
{
"@odata.type": "#microsoft.graph.onlineMeeting",
"allowAttendeeToEnableCamera": true
}
response:
{
"error": {
"code": "InvalidArgument",
"message": "One or more properties do not support updating. Please refer to Microsoft Graph documentation for more information.",
"innerError": {
"date": "2026-05-11T09:52:54",
"request-id": "c33e69dd-de32-4030-a393-d6cd63a449ea",
"client-request-id": "c33e69dd-de32-4030-a393-d6cd63a449ea"
}
}
}
as a workaround I have used object.getBackingStore().clear(); just after its creation before passing it to the patch. This will delete the parameter "@odata.type": "#microsoft.graph.onlineMeeting" making it work again.
EDIT 2026-05-11 08:07:00: at the moment issue seems to have been fixed.
Expected behavior
PATCH https://graph.microsoft.com/v1.0/users/<owners_uid>/onlineMeetings/
{
"@odata.type": "#microsoft.graph.onlineMeeting",
"allowAttendeeToEnableCamera": true
}
returns 200 with updated onlineMeeting
How to reproduce
try to patch an existing meeting using the java sdk for example setting the parameter allowAttendeeToEnableCamera
sdk under the hood will automatically add
"@odata.type": "#microsoft.graph.onlineMeeting"
to the http patch
it used to work in the past, but since a couple of days it returns:
"error": {
"code": "InvalidArgument",
"message": "One or more properties do not support updating. Please refer to Microsoft Graph documentation for more information.",
SDK Version
6.64.0
Latest version known to work for scenario above?
No response
Known Workarounds
as a workaround I have used object.getBackingStore().clear(); just after its creation before passing it to the patch. This will delete the parameter "@odata.type": "#microsoft.graph.onlineMeeting" making it work again.
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, die PATCH-Anfrage an den onlineMeetings-Endpunkt mit Java SDK 6.64.0 zu reproduzieren, wobei du allowAttendeeToEnableCamera verwendest und beobachtest, ob @odata.type gesendet wird. Vergleiche die Anfrage mit der dokumentierten erwarteten 200-Antwort und dem getBackingStore().clear()-Workaround; abgeschlossen ist die Aufgabe, wenn PATCH gelingt, ohne den backing store manuell zu leeren.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- api
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100