-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected]
Field Missing Error in Microsoft Graph API /chats POST Request
#2577
Comments
Thanks for raising this @julianmaurice Any chance you can confirm again the version of the SDK you are using? The issue mentions |
Ah, sorry for the confusion. I updated the post to clarify that the issue is with the request body. Specifically, I am including [email protected] in the AdditionalData, but the API responds with the error. |
Thanks for confirming Are you able to get the json response payload and use it to make a similar request on the Graph Explorer? var jsonString = KiotaJsonSerializer.SerializeAsString(chatRequestBody); |
Ah, very nice! This snippet allowed me to see that the request sent by the client was correctly formatted. I realized that the mistake was in my code. Thank you for your help! |
Describe the bug
I am encountering an issue with the Microsoft Graph API when attempting to create a new chat using the /chats POST request. The request fails with the following error message:
Despite ensuring that the [email protected] field is correctly formatted and included in the request, the API still returns this error. This problem has only recently started occurring, and the same code was functioning correctly before.
Expected behavior
The chat should be created successfully, with the members specified in the Members list being correctly added to the chat.
How to reproduce
Steps to reproduce the behavior:
SDK Version
5.56.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```The text was updated successfully, but these errors were encountered: