-
Notifications
You must be signed in to change notification settings - Fork 246
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
Multiple Notifications sent When Graph API SDK Patch Sent #1996
Comments
Thanks for raising this @noelrfMcM According to the documentation, you want only to have the Any chance you get a different result if you set the body as below to only update the specfied property? var requestBody = new Event
{
Attendees = attendees
}; |
Eastman,
Thanks for coming back to me. I will check if just adding the attendees makes a difference regarding the notifications.
I'll let you know if that makes a difference.
Thanks
Noel
From: Eastman ***@***.***>
Sent: Thursday, July 6, 2023 10:25 AM
To: microsoftgraph/msgraph-sdk-dotnet ***@***.***>
Cc: Noel McMahon ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoftgraph/msgraph-sdk-dotnet] Multiple Notifications sent When Graph API SDK Patch Sent (Issue #1996)
WARNING: External Email
Thanks for raising this @noelrfMcM<https://github.com/noelrfMcM>
According to the documentation, you want only to have the attendees property in the request payload for this to work as you wish. https://learn.microsoft.com/en-us/graph/api/event-update?view=graph-rest-1.0&tabs=http#notes-for-updating-specific-properties
Any chance you get a different result if you set the body as below to only update the specfied property?
var requestBody = new Event
{
Attendees = attendees
};
—
Reply to this email directly, view it on GitHub<#1996 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBARLIPJPMCJKECTUUR5AYDXOZ763ANCNFSM6AAAAAAZ4LRM54>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
1 similar comment
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
I had the same issue and I can confirm that this works. |
Describe the bug
currently using Microsoft Graph v 5.3.0. I have a web service written in .net core 6.0
to update Events in outlook by adding an attendee or removing it as required. I am also forwarding events to other emails.
The attendee is a room location resource email which is set to auto accept if free and auto decline if busy.
The trigger is a room booking system database change so we know the attendee to add then run the code.
The code is very much as per Microsoft example:
var graphClient = initialiseGraphClient(tenantId, clientId, secretName, keyVaultName, keyVaultURL);
When I do a patch to update the attendee list (remove or add an attendee), notifications are not only sent to the host but also
all the attendees. In some cases this can be 3 notifications at once with the same status of the new attendee has accepted.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Only one notification should be sent.
Screenshots
If applicable, add screenshots to help explain your problem.
Server:
The text was updated successfully, but these errors were encountered: